unify error messages

7/26/2019 Unify Error Messages

1/273

ACCELL/SQL:Error Messages


2/273

2


3/273

3

About This Manual v. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Error Message Descriptions 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ACCELL/SQL Combiner ( ACMB ) Error Messages 3. . . . . . . . . . . . . . . .ACCELL/SQL Linker ( ALNK ) Error Messages 16. . . . . . . . . . . . . . . . . . .ACCELL/SQL Compiler ( ACPL ) Error Messages 24. . . . . . . . . . . . . . . . .ACCELL/M anager ( AMGR ) Error Messages 87. . . . . . . . . . . . . . . . . . . . .ACCELL/SQL Interactive Debugger Error Messages 129. . . . . . . . . . . . . .

ACCELL/M anager Error Messages 133. . . . . . . . . . . . . . . . . . . . . . . . . . . .ACCELL/G enerator ( AGEN ) Error Messages 145. . . . . . . . . . . . . . . . . . . .ACCELL/SQL Utilities Error Messages 178. . . . . . . . . . . . . . . . . . . . . . . . .ACCELL/SQL Report Writer ( RPT ) Error Messages 185. . . . . . . . . . . . . . .ACCELL/SQL Menu Handler Error Messages 199. . . . . . . . . . . . . . . . . . . .ACCELL/SQL RDBMS Interface Error Messages 201. . . . . . . . . . . . . . . . .

Alphabetic Index 229. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Numeric Index 253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


4/2734


5/2735

describes the messages that may be

displayed while you are using ACCELL/SQL . Each message descriptionincludes the message text and number, the possible causes, and solutions.

This manual uses various graphic conventions to help you easilydistinguish between what you type in, the keys you press, the kind of information that appears on your screen, and the different elements of ACCELL/SQL .

Screen Displays

Forms, prompts, and other information that are displayed on the terminalscreen are represented in a screen outline, for example:

COMPANY:

ADDRESS:

CITY:MAIN PHONE:CONTACT:

SALES REP#:

NAME:PHONE:STATE: ZIP:

MAP:

Item NamesReferences to program names, database table and column names, screenform names, and form field names appear in bold typeface, for example:

To define a form, you fill in the Form Definition form with theappropriate information.

You use the same procedure to define the address_1 andaddress_2 fields that you used to define the co_name field.

The Target Table field lets you specify which database table thisform will directly query and update.

GraphicConventions


6/273

6

Keyboard Keys

A word or letter framed to look like a key indicates the correspondingkey on your keyboard, for example:

Represents the return key. This key could be labeled asEnter, RTN , or .

ACCELL/SQL Commands

A word or words that appear in bold, italic, sans serif typeface indicatesan ACCELL/SQL command that you can execute, for example:

Press , then .

To use an ACCELL/SQL command, you press a specific key or

sequence of keys. Because of the flexibility of ACCELL/SQL , youcan assign commands such as to different functionkeys, for instance .

This manual uses the following syntax conventions to describe theformat of ACCELL/SQL statements and functions, RPT statements, andoperating system command-level commands:

boldface Boldface words are command keywords or literal stringsthat you must type exactly as shown.

italic words Italic words indicate words, variables, numbers, orexpressions that you must provide. Examples are tablenames, column names, and constants.

Italic words are also used for manual names and termsdefined in the glossary. All-uppercase italics are used forconfiguration variable names.

UPPERCASE UPPERCASE words are ACCELL/SQL keywords.ACCELL/SQL keywords are not case sensitive: you cantype either uppercase or lowercase letters.

$ All ACCELL/4GL functions are suffixed by a dollar sign

($). The dollar sign distinguishes an ACCELL/4GLfunction from a user-defined function. Do not includeuse a dollar sign when you call your own functions.

SyntaxConventions


7/273

7

[ ] Non-bold square brackets indicate that the enclosed wordor item is optional and may be left out. Boldfacebrackets, [ ], are syntax elements that must be included,as in count[ character ].

|| Vertical bars that enclose a stacked list of options meanthat you can choose one of the listed options, but only

one of them.

. . . Ellipsis points indicate that you may repeat theimmediately preceding item any number of times, asneeded.

The manual also uses the following symbols to indicate special types of information:

TipTip contains helpful information.

WarningWarning cautions against actions that could cause data loss or damage tothe data base.

Additional Help Additional Help tells you where to find more information aboutdescribed topics.

OtherConventions


8/273

8


9/273

9

Error Message Descriptions


10/273

10 Error Message Descriptions

The ACCELL/SQL error messages that are described in this manual aregrouped by category: compiler, linker, ACCELL/ Manager, and so on.Error message descriptions include the text of the error message, anexplanation of the probable cause, and suggestions for correcting theproblem. Each error message entry has this format:

The error message number corresponds to the number of the errormessage text in the message file, $UNIFY/ unify.msg .On-screen, the error message number is displayed in parentheses at theend of the error message text or in the upper right corner of the errorform when error messages are displayed in a pop-up window.

In the error message text, italicized words are substitution markers.When the error message displays on the screen, the substitution markersare replaced by actual string or numeric values that apply to theindividual error condition. For example, in message 8317 thesubstitution markers variable_name would be replaced by the name of

the variable that has the type conflict.

Error messages are listed numerically, by the error message number. If you do not know the error message number, see the Alphabetic Indexon page NO TAG to obtain the number. Alphabetic Index lists the

error messages alphabetically by error message text.

If you follow the instructions in the suggested correction and are stillunable to resolve the error, please call Customer Support for assistance.Make sure that you have the error message number available whencalling.


11/273

11 ACCELL/SQL Combiner (ACMB) Error Messages

ACCELL/SQL Combiner (ACMB) ErrorMessages

The following messages may be displayed while you are combining an

ACCELL/SQL application.

8201 SAR ERROR : There is a corrupt archive file archive_name .

This error indicates that a recently created archive file was successfullycreated. However, the archive was corrupt when the ACCELL/SQLcombiner, ACMB , attempted to read the archive.

This error can occur in these cases:

The application directory does not contain enough disk space tocreate the archive file, and no error status was returned by theoperation system.

The newly create archive file was modified by some outsidesource before ACMB read the file.

Make sure that the application directory contains enough disk space, thenrebuild the archive by using ACMB or ACCELL/E nvironment.

8205 SAR ERROR : Cannot open archive_name , error number os_error .

The ACCELL/SQL combiner ( ACMB ) could not open the archive filenamed archive_name , in the current directory. This archive file can beeither a new archive file or a temporary archive file.

The error number, os_error , is the error status returned by the operating

system. See your system error file for a list of error numbers.Make sure that you have read and write permission in the currentdirectory and that the current directory has enough space to create a newarchive file.

8206 SAR ERROR : Cannot create archive_name , error number os_error .

The ACCELL/SQL combiner ( ACMB ) could not create the archive filenamed archive_name in the current directory. This archive file can beeither a new archive file or a temporary archive file.

Explanation

Correction

Explanation

Correction

Explanation


12/273


The error number, os_error , is the error status returned by the operatingsystem. See your system error file for a list of valid error numbers.

Make sure that you have read and write permission in the currentdirectory and that the current directory has enough space to create a newarchive file.

8207 SAR ERROR : Cannot close archive name , error number os_error .

The ACCELL/SQL combiner ( ACMB ) failed to close the temporaryarchive named archive name , which was created to build a new archive.This error can occur when the host operating system has a problem or thecombiner has an internal system error.

The error number os_error is the error status returned by the operating

system. See your system error file for a list of valid error numbers.If this error persists, contact Unify Customer Support.

8208 SAR ERROR : Error reading file_name , error number error# .

The combiner was unable to read a form from the existing archive file.

Make sure that the current user has read permission for the archive file. If the problem persists, remove the archive and rebuild the application.

8209 SAR ERROR : Error adding file_name , error number error# .

The combiner was unable to add a form to an existing archive file.

Make sure that the current user has read permission for the archive file. If the problem persists, remove the archive and rebuild the application.

8210 SAR ERROR : Error renaming file_name to file_name .

The combiner was unable to rename a file to the specified file name aftercreating a new archive in a temporary file.

Make sure that the archive files and directories have the correctpermissions and sufficient space. If the problem persists, remove thearchive and rebuild the application.

Correction

Explanation

Correction

Explanation

Correction

Explanation

Correction

Explanation

Correction


13/273


8300 ACMB ERROR : There was an error in reading the file file_name .

The ACCELL/SQL combiner ( ACMB ) cannot read an ACCELL/SQL formfile (a .fq or .aq file) and the form is not a global function, or thecombiner cannot find and read a form file or a script file for file_name .This error occurs in one of these cases:

The .fq or .aq file could not be opened or closed. Either the filedoes not exist, or you do not have read and write permission forthe file.

The .fq or .aq file can be opened, but the file is corrupted.

The maximum number of file descriptors allowed for a process hasbeen reached.

The system is out of memory.

Make sure that the file exists and that you have read and writepermission for the indicated file.

To determine whether or not the file is corrupted, try running Q2ASC if the file is a form file (a .aq or .fq file). If the file is a script file (a .as or.fs file), run ACPL to produce a new .ao or .fo file.

TipIf your system is configured with the minimum memory requirements forACCELL/SQL or you are running on a heavily loaded system, ACMB canfail to allocate the memory needed to combine both form and objectcode. This situation can occur when a form has an excessive number of fields (over 100) and large form scripts of over 1000 lines. In this case,

you must reduce the complexity of the form or form script.

8301 ACMB ERROR : There was a bad magic number.

The ACCELL/SQL combiner ( ACMB ) has encountered an unknownmagic number in an ACCELL/SQL file. Every ACCELL/SQL file type hasan associated magic number that enables executables to distinguishbetween different types of files.

Explanation

Correction

Explanation


14/273


This error can occur in these cases:

The combiner has been asked to open a file that is not an archivefile.

The file may have been corrupted by some system or programfailure.

The user has made an execution error.

Make sure that you have specified the correct archive file name. Tryremoving the archive file and running ACMB again.

8302 ACMB ERROR : The Combine failed in malloc memory.

The ACCELL/SQL combiner ( ACMB ) has run out of memory whiletrying to combine the form file and optional object file. This error canoccur when ACMB is combining forms with a large number of screenfields (over 100) and form scripts that contain a large number of lines(over 1000).

The form (the .aq or .fq file) and the object code (the .ao or .fo file) arerepresented by a structure referred to as a form unit . An ACCELL/SQLarchive file ( .fa file) can be thought of as a collection of form units.

Three main areas affect form unit memory requirements:

the symbol table (the collection of all fields and variables in theform unit)

code space (all ACCELL/4GL statements in the .ao or .fo file, plusthe object code that is generated automatically by the generatorwhen you defined the form)

the literal pool (all string constants for a form unit)

This error can also be caused by insufficient memory or swap spaceavailable at the time you ran the combiner. This situation can occur onheavily loaded systems.

Reduce the memory requirements of the form unit by reducing the size of any of the three areas in the previous list. If the memory insufficiencywas a temporary condition at execution time, try running the combineragain.

Correction

Explanation

Correction


15/273


8303 ACMB ERROR : Couldnt find a next field.

When the ACCELL/SQL generator creates an ACCELL/SQL form file (a.fq or .aq file), the generator creates a list of the forms screen fields.Indexes into this list are used to set the initial next field attribute for eachfield in the list.

The ACCELL/SQL combiner ( ACMB ) creates a temporary file thatcontains information for a form from the .fq / .fo, or .aq / .ao file pair. Oneof the steps in creating this file is to change the initial NEXT_FIELDattribute for each field in the list so that it indexes the symbol table builtfrom information in the .fo / .ao and .fq / .aq files.

This error occurs when the combiner cannot find a symbol table entry fora field in the list created by the generator.

Make sure that no statement that sets the NEXT_FIELD attribute sets theattribute to a non-existent field.

8304 ACMB ERROR : Checksum error. Verify .fs and .fq target tablenames match.

When the ACCELL/SQL combiner ( ACMB ) is processing a form that hasa form script, it verifies that the checksum stored in the script filematches the checksum in the form file. This error can occur in thesecases:

Either the script file contains a target table name that is not in theform file, or the form file contains a target name that is not in thescript file.

The database design was changed, and one of the files has notbeen rebuilt; that is, this file is out of date.

Make sure the target table name is the same for both the form file namedon the Form Definition form and the script file named in the FORMsection.

If the error persists, run the form file first through Q2ASC then throughASC2Q to recompute the checksum; or edit the form file with thegenerator to achieve the same result. To recompute the checksum for theobject file, recompile the object file with ACPL .

Explanation

Correction

Explanation

Correction


16/273


Even if the script file does not refer to a database column that has beenadded to the target table, the file must still be recompiled so that itschecksum can be calculated according to the updated database design.

8305 ACMB ERROR : The field field_name is not in the file file_name .[af]q.

When the ACCELL/SQL compiler ( ACPL ) compiles a form script file, itcreates a list of all screen fields that are referenced by the script andstores the list in the resulting object file. When the generator ( AGEN )creates a form file, it also creates a list of all the screen fields for theform.

When the ACCELL/SQL combiner ( ACMB ) combines a form and its formscript, it verifies that each field listed in the script is actually in the formfile. The combiner reports the offending field ( field_name ) and the name

of the form file that was searched ( file_name ).

The most common cause of this error is the declaration of a FIELDsection that lists an invalid field.

Verify the spelling of the field names listed in the FIELD sections and instatements that reference fields. Also make sure that you have defined thefield name that you are using.

8306 ACMB ERROR : There was a form name mismatch.

When the ACCELL/SQL combiner ( ACMB ) is processing a form that hasa form script, ACMB makes sure that the form or application name storedin the object ( .fo / .ao ) file matches the form or application name stored inthe form file ( .fq / .aq ).

This error occurs if the combiner discovers an inconsistency.

If you are combining a standard form file and form script file, make surethe FORM section in the form script file lists the same form name asspecified on the ACCELL/SQL generator Form Definition form for thestandard form.

If you are combining a master application form file and form script file,make sure that the APPLICATION section in the form script file lists thesame application name as specified on the ACCELL/SQL generator FormDefinition form for the master application form.

Explanation

Correction

Explanation

Correction


17/273


8307 ACMB ERROR : There was a form/application mismatch.

When the ACCELL/SQL combiner ( ACMB ) is processing a form that hasa form script, ACMB makes sure that the form file ( .fq / .aq ) and thecorresponding object file ( .fo / .ao ) both specify the same type of form(master application or standard). This error occurs if the combinerdiscovers an inconsistency.

Make sure that both the form file and the form script file are for the sametype of form: standard or master application.

8308 ACMB ERROR : There is a corrupt file.

The ACCELL/SQL combiner ( ACMB ) cannot read all or part of thearchive index for an ACCELL/SQL archive file ( .fa file).

Delete the existing archive file ( .fa ) and rebuild it with ACMB . Forinformation on how to use ACMB to build an archive file, see the ACMBsyntax and usage description in

.

8309 ACMB ERROR : There was an error in adding the form.

The ACCELL/SQL combiner ( ACMB ) cannot write a form unit in anACCELL/SQL archive file.


This error can occur in one of these cases:

The combiner cannot add a new form unit. The combiner creates anew form unit from information in the .fo / .fq or .ao / .aq file pair,writes this structure to a temporary archive file, then adds it to thearchive file. The attempt to create the temporary archive file failed.

Explanation

Correction

Explanation

Correction

Explanation


18/273


The combiner cannot add the form unit (either a pre-existing formunit or the new form unit stored in a temporary file) to an existingapplication archive file. The combiner reads in the existing formunits in the archive file, sorts them with the form unit for the formto be added to the archive, then writes all the form units to thearchive file.

Make sure that you have permission to write in the current directory andthat the directory contains enough space for a temporary copy of thearchive, plus a temporary copy of the combined form and code file. Also,if you are using the UNIX operating system, make sure that your ulimitis set high enough to allow the creation of the archive file.

8310 ACMB ERROR : The form name has multiple definitions.

As new form units are archived by the ACCELL/SQL combiner ( ACMB ),ACMB verifies that the form name is unique to the archive. This erroroccurs if the combiner encounters a duplicate form name.


Search the application directory for any form script files or form filesthat may contain duplicate form names. The form name in a form scriptis listed in the FORM section. The form name in a form file is listed onthe ACCELL/G enerator Form Definition form for the form.

8311 ACMB ERROR : There was an error in reading the form.

Once the ACCELL/SQL combiner ( ACMB ) has produced the temporaryfile of information from the forms .fo / .fq or .ao / .aq file pair, it eithermerges this information into the existing archive file or creates a newarchive file. This error occurs when the combiner is unable to merge thetemporary file information into the existing archive file. To create thenew archive, the combiner must be able to read the old archive entries inthe existing archive file.

Make sure you have read/write permission on the existing archive file(.fa ). If the permissions are correct, the archive is probably corrupted.Delete the existing archive file ( .fa ) and rebuild it with ACMB .

Correction

Explanation

Correction

Explanation

Correction


19/273


8312 ACMB ERROR : Warning: there was an illegal display variablename: variable_name .

Screen field names of the form fkey_prompt_ nn (where nn is anumber) are system variables that define ACCELL/SQL function keyprompts. The function key number, indicated by nn , must fall between 0and 99. This error occurs if nn is any number outside this range.

Edit the offending form file and change nn to a number between 0 and99.

8313 ACMB ERROR : There was an error opening file_name , errornumber os_error .

The ACCELL/SQL combiner ( ACMB ) could not open the file file_name .This file is probably one of the following files:

the existing archive file

the temporary form unit file

the temporary archive file

The error number os_error is either 11 , which indicates that there are nomore internal file descriptors, or an operating system error.

Take corrective action based on the os_error number provided:

If os_error is 11, see your system administrator aboutreconfiguring your operating system with more file descriptors.

Otherwise, make sure that you have read and write permission in

the current directory and on the existing archive file (the .fa file).

If the archive header is corrupted, recreate the archive with ACMB . Inthis case, the archive must be recreated from scratch. For informationabout using the ACMB utility, see

.

Explanation

Correction

Explanation

Correction


20/273


8314 ACMB ERROR : There was an error renaming temp_archive_name toexisting_archive_name .

The ACCELL/SQL combiner ( ACMB ) was unable to rename thetemporary file to the name of the existing archive file. The combinercreates a temporary archive before creating a new archive. On UNIX ,after the temporary file is complete, the combiner uses the link system

call to rename the temporary file. This error occurs if the link fails.

Make sure that you have read and write permissions in the currentdirectory.

8315 ACMB ERROR : There was an error creating file_name , errornumber os_error .

The ACCELL/SQL combiner ( ACMB ) could not create the temporary fileto be used to combine the form file and the object file. The error number,os_error , is the error status returned by the operating system. Consultyour system error file for a list of valid error numbers.

Make sure that you have read and write permissions in the currentdirectory.

8316 ACMB ERROR : There was an error closing a file, error numberos_error .

The ACCELL/SQL combiner ( ACMB ) could not close the temporary fileused to combine the form file and the object file. The error number,os_error , is the error status returned by the operating system. Consult

your system error file for a list of valid error numbers. This is an internalerror and should not occur in the normal execution of ACMB .

If this error occurs, please call Unify Customer Support.

Explanation

Correction

Explanation

Correction

Explanation

Correction


21/273


8317 ACMB ERROR : Type conflict on target variable variable_name .

On certain RDBMS products, the data types of target ACCELL/SQLvariables can be chosen by the developer in the generator or in a formscript file. This error indicates that the specified data types areincompatible between the generator and compiler or betweenACCELL/SQL and the database.

Make sure that the data types specified for target variables in thegenerator and compiler are compatible with each other and with theRDBMS data type of the target column.

8318 ACMB ERROR : The DBTYPE configuration variable is not set or isset incorrectly.

ACCELL/SQL could not access its own information about the currentdatabase product it is to interface with. This error should not normallyoccur.

Make sure that the DBTYPE configuration variable is set correctly. If it is,please contact Unify Customer Support.

8319 ACMB ERROR : table name used as target table in 4GL , no target

table declared in generator.

A target table was specified in the form script FORM header, but notarget table was specified when the corresponding form was generated.

Remove the TARGET_TABLE clause from the form script FORMheader, or regenerate the form and add the appropriate target table on theForm Definition form.

8320 ACMB ERROR : table name used as target table in AGEN , no targettable in 4GL .

A target table was specified on the Form Definition form inACCELL/G enertor, but no TARGET_TABLE clause was used in the formscript FORM header of the corresponding form script.

Add a TARGET_TABLE clause to the form script FORM header, orregenerate the form and remove the target table specified on the FormDefinition form.

Explanation

Correction

Explanation

Correction

Explanation

Correction

Explanation

Correction


22/273


8321 ACMB ERROR : table name used as target table in AGEN ,table_name used as target table in 4GL.

The target table specified on the Form Definition form is different fromthe table specified in the TARGET_TABLE clause of the form scriptFORM header.

After determining the correct target table for the form, modify the targettable name on the Form Definition form, or change the table namespecified in the TARGET_TABLE clause of the form script FORMheader.

8322 ACMB ERROR : Number of target columns known to .fq and .fo fortable table name do not match.

Between the time ACCELL/G enerator was run and the compiler was runthe number of columns in the specified table have changed.

Rerun ACCELL/G enerator on the screen form ( .fq file) and recompile theform script ( .fs file). Then rerun the combiner.

8323 ACMB ERROR : Columns in target table table name for .fq and .fodiffer.

Between the time ACCELL/G enerator was run and the compiler was runthe names of some of the columns in the specified table have changed.

After removing obsolete columns, rerun ACCELL/G enerator on thescreen form ( .fq file) and recompile the form script ( .fs file). Then rerunthe combiner.

WarningIf the original form contains target fields that are no longer in thetarget table, ACCELL/G enertor changes these fields to non-targetscreen fields.

Explanation

Correction

Explanation

Correction

Explanation

Correction


23/273


8324 ACMB ERROR : The characteristics of column column name aredifferent in the .fq and .fo.

Between the time ACCELL/G enerator was run and the compiler was runthe characteristics of some of the columns in the specified table havechanged.

Rerun ACCELL/G enerator on the screen form ( .fq file) and recompile theform script ( .fs file). Then rerun the combiner.

WarningIf the original form contains target fields for columns that havechanged, ACCELL/G enerator changes these fields to match thedatabase definitions.

8325 ACMB ERROR : There was a class mismatch for field field_name .

The dimensions of an array were specified differently inACCELL/G enerator and an ACCELL/4GL form script. The dimensions of a screen array (1 for a list or 2 for a matrix) can be specified throughACCELL/G enerator and in an ACCELL/4GL form script.

Make sure that the dimensions of the arrays defined inACCELL/G enerator match the dimensions specified for the same arrays inACCELL/4GL form scripts.

8326 ACMB ERROR : The local array array_name was not defined.

A symbol that is local to the form being combined was referenced as anarray in an ACCELL/4GL form script, but the array was not defined aslocal in the ACCELL/4GL form script or in ACCELL/G enerator.

Locate the reference and change it to reference an existing array, ordefine the array that is being referenced. Arrays can be defined inACCELL/G enerator or in an ACCELL/4GL form script.

Explanation

Correction

Explanation

Correction

Explanation

Correction


24/273

24 ACCELL/SQL Linker (ALNK) Error Messages

ACCELL/SQL Linker (ALNK) ErrorMessages

8401 ALNK ERROR : The application linker does not have enoughmemory.

The ACCELL/SQL linker ( ALNK ) tries to read information from theappropriate archive file for each application form. This error occurs whenthe linker is unable to allocate space in which to read the information andindicates that the linker has run out of system memory.

This error can occur under one of these conditions:

Not enough system memory is available when you execute thelinker.

You have a large number of form units (over 100) in the samearchive file.

A form unit is the structure used by ACCELL/SQL to represent the form(the .aq or .fq file) and the object code ( the .ao or .fo file). Think of anACCELL/SQL archive file ( .fa file) as a collection of form units.

If you suspect that not enough system memory was available at the timeyou executed the linker, try executing the linker again before trying tosplit the archive file. If you have a large number of form unit in thesame archive file, try splitting that archive into two archives.

8402 ALNK ERROR : There is a duplicate required form form_name inthe application.

The ACCELL/SQL linker ( ALNK ) sets up an internal table containinginformation about all application forms, including global functions. Thiserror occurs if the linker finds a duplicate entry for a required form in theinternal table.

Make sure that the REQUIRED FORMS and REQUIRED FUNCTIONSclauses of the APPLICATION section in the master application formscript contain no duplicate form or function names.

The application form is not treated as a required form. Therefore, theREQUIRED FORMS section may list a form that has the same name asthe application.

Explanation

Correction

Explanation

Correction


25/273


8404 ALNK ERROR : Form form_name is not in the archive or the archivedoesnt exist.

The form or function was listed in the REQUIRED FORMS orREQUIRED FUNCTIONS clause. However, the ACCELL/SQL linker(ALNK ) could not find the form_name form or function in the defaultarchive or any of the archives listed in the ARCHIVES clause of theAPPLICATION section in the master application script. Either thearchive could not be found or the form_name form or function was notarchived.

Take these steps:

1. Make sure that the form_name form or function is spelledcorrectly and is listed in the REQUIRED FORMS or REQUIREDFUNCTIONS clause in the APPLICATION section for the masterapplication form script.

2. Make sure that each archive listed in the ARCHIVES clause exists(in the current directory or in the directory indicated by the

ACLPATH configuration variable).

8405 ALNK ERROR : Error opening application archive filearchive_name , Status = status_value .

The ACCELL/SQL linker ( ALNK ) was unable to open the archive file ( .fafile), archive_name . This error can occur in these cases:

A misspelled or otherwise invalid archive file name has beenspecified in the REQUIRED FORMS section of the masterapplication form script. The archive name must include the .fa filename suffix.

The person who is trying to link the application does not havewrite permissions on the archive.

Explanation

Correction

Explanation


26/273


The archive file cannot be opened.

The archive file is corrupted.

The maximum number of file descriptors allowed per process hasbeen reached.

The status status_value indicates the cause of the failure. Status is set toone of these values:

an operating system error number, if the archive cannot be openedor is corrupted

11 , if the number of file descriptors has been exceeded

2, if the archive file header was corrupted

Try one of these solutions:

Make sure that the archive name is specified correctly in themaster application form script.

Make sure that you have read and write permissions on the archivefile archive_name .

If the file permissions are correct, the archive is probablycorrupted. Delete the existing archive file ( .fa ) and rebuild it withACMB . For information on how to build an archive file, see theACMB description in

.

If status_value is 11, see your system administrator aboutreconfiguring your operating system with more file descriptors.

8406 ALNK ERROR : Ran out of memory while allocating archive indexspace.

The ACCELL/SQL linker ( ALNK ) ran out of memory while trying to readin the archive index of an archive file ( .fa file).

Reduce the number of forms in the archive.

1. Split the archive into two smaller archives.

2. Modify the archive names in the REQUIRED FORMS ,REQUIRED FUNCTIONS , and ARCHIVES clauses of the masterapplication form APPLICATION section.

3. Recombine ( ACMB ) the archive and relink ( ALNK ) theapplication. For information about building an archive file, see theACMB description in

.

Correction

Explanation

Correction


27/273


8407 ALNK ERROR : There was an error reading an archive index, Status= os_error .

The ACCELL/SQL linker ( ALNK ) was unable to read in the archive indexfor an archive file ( .fa file). Status os_error is the error number returnedby the operating system.

Rebuild the archive file with ACMB . For information about building anarchive file, see the ACMB description in

.

8408 ALNK ERROR : The specified master application form form_name not in archive archive_name .

The ACCELL/SQL linker ( ALNK ) was unable to find an entry in thearchive file with an application name matching the application namespecified in the command line. The linker searches the archive file ( .fafile) specified in the command line for this application entry.

Make sure the application name and archive name specified in the ALNKcommand line are spelled correctly. Recombine the master applicationform with ACMB and relink the application. For information on how to

combine the master application form, see the ACMB description in .

8409 ALNK ERROR : Error closing an application archive file, Status =os_error .

The ACCELL/SQL linker ( ALNK ) was unable to close an archive file. If

the status os_error is 1 (EOF ), the close failed because the end of filewas reached. Otherwise, os_error is the status returned by the operatingsystem.

If you receive this error, please call Unify Customer Support.

Explanation

Correction

Explanation

Correction

Explanation

Correction


28/273


8410 ALNK ERROR : There was an error while reading a form file, Status= status_value .

The ACCELL/SQL linker ( ALNK ) cannot read the archive file. Thearchive file is probably corrupted. If not enough system memory isavailable, the status status_value is 5. Otherwise status_value is set tothe error number returned by the operating system.

A status_value of 5 can occur on a heavily loaded system. If yoursystem is heavily loaded try executing the linker again. Otherwise,rebuild the corrupted archive file with ACMB .

If your application has several archives take these steps:

1. Rebuild one archive.

2. Relink the application.

3. If the error occurs again, continue to rebuild an archive and relink the application until the error does not appear.

For information on how to build an archive file, see the ACMBdescription in

.

8411 ALNK ERROR : Ran out of archive name space.

The ACCELL/SQL linker ( ALNK ) keeps an internal table of all thearchive files that are used by the application. This error can occur whilethe linker is creating the table of archive names if either of these

conditions exist:The internal table has reached its ACCELL/SQL defined limit of 512 entries.

An attempt to allocate storage for an entry fails.

If you are using more than 512 archives in the application, reduce thenumber of archives being used. If you are running the linker on a heavilyloaded system, try running the linker again when the system load islighter.

Explanation

Correction

Explanation

Correction


29/273


8413 ALNK ERROR : ALNK : BAD Exit Status = error_number .

The ACCELL/SQL linker ( ALNK ) encountered an error while attemptingto link the application. This is a general error message and is usuallypreceded by another more specific message that indicates why the linkerfailed. Status error_number is the message number of the more specificerror message.

Check the preceding error messages for a more complete description of the error. Use these preceding messages and the status value to determinethe cause of the error.

8414 ALNK ERROR : Could not open or create the .al file.

The ACCELL/SQL linker ( ALNK ) cannot open or create the application

map file ( .al file). After the linker reads the information it needs from thearchive files, it tries to create or open the application map file. This erroroccurs if the linker cannot open or create the file.

Make sure that you have read and write permissions for the applicationdirectory that contains the application map file ( .al ). Verify that theapplication directory contains enough space to hold the new ( .al ) file.

8415 ALNK ERROR : There was an error while closing the .al file, Status =os_error .

The ACCELL/SQL linker ( ALNK ) was unable to close the newly createdapplication file. The status os_error is the error number returned by theoperating system. This is an internal error and should not occur in thenormal linking of an ACCELL/SQL application.


8416 ALNK ERROR : There was an error while seeking or writing the .alfile.

The ACCELL/SQL linker ( ALNK ) found a corrupted application map file(.al file).

Delete the application map file ( .al ) and execute ALNK again to recreatethis file.

Explanation

Correction

Explanation

Correction

Explanation

Correction

Explanation

Correction


30/273


8418 ALNK ERROR : Could not find the form_name form in thearchive_name archive.

The ACCELL/SQL linker ( ALNK ) cannot find an entry for the form_nameform or function in the archive archive_name . For each form or functionlisted in the REQUIRED FORMS or REQUIRED FUNCTIONS clause of the APPLICATION section, the linker verifies that the form or function is

listed in the specified archive file.

Verify that the spellings of the form name or function name and thearchive name in the REQUIRED FORMS or REQUIRED FUNCTIONSclause of the APPLICATION section are correct. Recombine the

form_name form or function in the archive archive_name by usingACMB . For information about building an archive file, see the ACMBdescription in

.

8419 ALNK ERROR : Ran out of archive names getting checksums.

This is an internal error and should not occur in the normal linking of anACCELL/SQL application.


8420 ALNK WARNING : Form form_name could not be found in anarchive.

The ACCELL/SQL linker could not find the form form_name in thedefault archive or any of the archives listed in the ARCHIVES clause of

the APPLICATION section in the master application form script. This issimply a warning message. The form form_name was not specified in aREQUIRED FORMS clause but was referenced by a form in theapplication.

Explanation

Correction

Explanation

Correction

Explanation


31/273


Take these actions:

If the form will not be accessed at runtime (the path of theapplication it is on will not be accessed) then no action is needed.

If the form is to be accessed at runtime, make sure that the form form_name is spelled correctly. Also make sure that the archivecontaining it is listed in the ARCHIVES clause or make sure thatthe form and its archive is specified in the REQUIRED FORMSclause.

Make sure that the archive exists in the current directory or in thedirectory indicated by the ACLPATH configuration variable).

If the ARCHIVES or the REQUIRED FORMS clause is notcorrect, edit the clause, recompile ( ACPL ) the master applicationscript, recombine ( ACMB ) the master application form, and relink the application.

If the master application script is correct, try archiving theindicated form again.

Correction


32/273

32 ACCELL/SQL Compiler (ACPL) Error Messages

ACCELL/SQL Compiler (ACPL) ErrorMessages

8501 ACPL ERROR : A ( operator was expected.

The ACCELL/SQL compiler ( ACPL ) expected a left parenthesis, (, in aform script statement or section.

The left parenthesis is required in these locations:

after the keyword FOR in a FOR statement

after the function name or stored procedure name and before anyarguments in a function call or stored procedure call (Theparentheses are required even if the function or stored procedurehas no arguments.)

after the function name and before any function parameters in aFUNCTION statement: either a local or global functiondeclaration. (The parentheses are required even if the function hasno parameters.)

in an AT clause before the row and column coordinates (The ATclause can appear in the DISPLAY , ENABLE ZOOM , DISPLAYTRIM , and ERASE TRIM statements, and, for GUI options, in theBUTTON LOCATION clause of the DEFINE COMMANDstatement.)

Find the form script statement that is missing the parenthesis, and rewritethe statement. See the forthe syntax and usage of form script statements and sections.

8502 ACPL ERROR : A ) operator was expected.

The ACCELL/SQL compiler ( ACPL ) expected a right parenthesis, ), ina form script statement or section.

Explanation

Correction

Explanation


33/273


The right parenthesis is required in these locations:

after the last expression to be evaluated in a FOR statement

after the arguments in a function call or stored procedure call (Theparentheses are required even if the function or stored procedurehas no arguments.)

after the function parameters in a FUNCTION statement: either alocal or global function declaration (The parentheses are requiredeven if the function has no parameters.)

in an AT clause after the row and column coordinates (The ATclause can appear in the DISPLAY , ENABLE ZOOM , DISPLAYTRIM , and ERASE TRIM statements, and, for GUI options, in theBUTTON LOCATION clause of the DEFINE COMMANDstatement.)

at the end of an expression that is introduced by a left parenthesis,

(

Find the form script statement that is missing the right parenthesis, andrewrite the statement. See the

for the syntax and usage of form script statements andsections.

8503 ACPL ERROR : A , was expected.

The ACCELL/SQL compiler ( ACPL ) expected a comma ( ,) in a formscript statement.

The comma is required in these locations:

in the AT position clause between the row and columncoordinates. (The AT clause can appear in the DISPLAY , ENABLEZOOM , DISPLAY TRIM , and ERASE TRIM statements, and, forGUI options, in the BUTTON LOCATION clause of the DEFINECOMMAND statement.)

in the MATRIX declaration between the row and columnspecifications

between parameters in a function definition

Find the form script statement that is missing the comma, and rewrite thestatement. See the for thesyntax and usage of form script statements and sections.

Correction

Explanation

Correction


34/273


8504 ACPL ERROR : A form or function name exceeded 15 characters inlength.

You have specified more characters than allowed for a form or functionname. These are the allowed lengths:

Form names and global function names can be up to 15 characters

long.Local function names and C-hook function names can be up to 44characters long.

Stored procedure names can be up to 44 characters long if allowed bythe RDBMS . If the RDBMS limits stored procedure names to fewerthan 44 characters, ACCELL/SQL allows the RDBMS limit. If theRDBMS allows stored procedure names to be more than 44 characters,

ACCELL/SQL uses the 44-character limit.

Make sure that form names and global function names are 15 charactersor less. Make sure that local function names and C-hook function namesare 44 characters or less. Make sure that stored procedure names are 44characters or less and not more than the number of characters allowed bythe RDBMS .

8505 ACPL ERROR : A : was expected.

The ACCELL/SQL compiler ( ACPL ) expected a colon ( :) in a formscript statement.

The colon is required in these locations:

after the constant specified in a CASE clause of a SWITCHstatement

after the command name in the SET COMMAND statement

after the DEFAULT keyword in a SWITCH statement

Find the form script statement that is missing the colon, and rewrite the

statement. See the for thesyntax and usage of form script statements and sections.

Explanation

Correction

Explanation

Correction


35/273


8506 ACPL ERROR : A ; was expected.

The ACCELL/SQL compiler ( ACPL ) expected a semicolon ( ;) in a formscript statement.

The semicolon is required in these locations:

at the end of the DELETE SELECTED ROW , SLOCK , UNLOCK ,and XLOCK statements

after the expression to be evaluated once at the beginning of theloop in a FOR statement (The semicolon is required even if noexpression is specified.)

after the expression to be evaluated at the beginning of each loopiteration in a FOR statement (The semicolon is required even if noexpression is specified.)

Find the form script statement that is missing the semicolon and rewritethe statement. See the forthe syntax and usage of the DELETE SELECTED ROW , FOR , SLOCK ,UNLOCK , and XLOCK statements.

8512 ACPL ERROR : The BEGIN keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theBEGIN keyword. The BEGIN keyword is required in these locations:

before the statements in an EXECUTING clause of the SELECTstatement

after the expression following the SWITCH keyword in aSWITCH statement

Find the form script statement that is missing the BEGIN keyword andrewrite the statement. See the

for the syntax and usage of form script statements.

Explanation

Correction

Explanation

Correction


36/273


8517 ACPL ERROR : The END keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theEND keyword. The END keyword is required in these locations:

after the statements in an EXECUTING clause of the SELECTstatement

at the end of a SWITCH statement

Find the form script statement that is missing the END keyword, andrewrite the statement. See the

for the syntax and usage of form script statements.

8518 ACPL ERROR : The FIELD keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theFIELD keyword. The FIELD keyword is required in these locations:

after the RESTART ON keywords in a RESTART ON FIELDstatement

after the WHEN keyword in a WHEN FIELD CHANGESsubsection

after the INIT keyword in an INIT FIELD subsection

Find the form script statement or section that is missing the FIELDkeyword, and rewrite the statement or section. See the

for the syntax and usage of form scriptstatements and sections.

8520 ACPL ERROR : The FORM keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theFORM keyword. The FORM keyword is required in these locations:

after the NEXT keyword in a CHOOSE NEXT FORM section, if the form is a standard form

after the FIRST keyword in a CHOOSE FIRST FORM section, if the form is a master application form

Find the form script statement or section that is missing the FORM

keyword, and rewrite the section. See the for the syntax and usage of event sections.

Explanation

Correction

Explanation

Correction

Explanation

Correction


37/273


8522 ACPL ERROR : The FROM keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theFROM keyword. The FROM keyword must follow the variable name inthe RETRIEVE statement.

Find the RETRIEVE statement that is missing the FROM keyword, andrewrite the statement. See

for the syntax and usage of the RETRIEVE statement.

8523 ACPL ERROR : The FUNCTION keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theFUNCTION keyword. The FUNCTION keyword must follow the returntype in either a global or a local function declaration.

Find the function declaration that is missing the FUNCTION keyword,and rewrite the statement. See the

for the syntax and usage of the FUNCTION section.

8524 ACPL ERROR : A field ID was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be thename of a field variable or a target field variable. A field variable nameor target field variable name must be specified in a FIELD section.

Find the form script statement or section that is missing the field name.Also verify the use of variable names that are not field names. Rewritethe statement or section. See

for the syntax and usage for form script statements andsections.

8525 ACPL ERROR : A file ID was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be anoperating system file name, which specifies the name of the archivewhere the form or function is stored. The archive file name must followthe IN keyword in the REQUIRED FORMS or REQUIRED FUNCTIONSclauses of the APPLICATION section (in the master application script).

Rewrite the REQUIRED FORMS or REQUIRED FUNCTIONS clause of the APPLICATION section (the master application header) in the form

script script file. See forthe syntax and usage of the APPLICATION section.

Explanation

Correction

Explanation

Correction

Explanation

Correction

Explanation

Correction


38/273


8526 ACPL ERROR : A form ID was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be a formname or function name. In the REQUIRED FORMS or REQUIREDFUNCTIONS clause of the APPLICATION section in the masterapplication script, each form or function specification must begin with aform name or function name.

Rewrite the REQUIRED FORM or REQUIRED FUNCTIONS clause of the APPLICATION section in the master application form script scriptfile. See for the syntaxand usage of the APPLICATION section.

8527 ACPL ERROR : A form, application or user function definition wasexpected.

The ACCELL/SQL compiler ( ACPL ) could not find a valid statement atthe beginning of a form script file.

For the master application form script file (the .as file), anapplication definition must appear in the APPLICATION section.

For a standard script file (a .fs file), either a form definition mustappear in the FORM section, or an external declaration mustappear in the EXTERN and FUNCTION statements.

Start a standard form script file with either a form declaration (the FORMsection) or an external declaration (the EXTERN and FUNCTIONstatements). Start a master application form script file with an applicationdeclaration (the APPLICATION section). See

for the syntax and usage of form script statementsand sections.

8528 ACPL ERROR : Display location was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be adisplay location: either a screen field name or the FYI_MESSAGEkeyword. The display location must follow the FOR keyword in theDISPLAY statement.

Find the DISPLAY statement that is missing the display location, andrewrite the statement. Omit the FOR clause or follow the FOR keywordwith either a field name or the FYI_MESSAGE keyword. See

for the syntax and usageof the DISPLAY statement.

Explanation

Correction

Explanation

Correction

Explanation

Correction


39/273


8529 ACPL ERROR : The IN keyword was expected.

The IN keyword was missing from the CREATE TIMER EVENTstatement.

Add the IN keyword to the CREATE TIMER EVENT statement. INshould be followed by an expression that specifies the minimum numberof seconds that must pass before the timer handler function is executed.

8532 ACPL ERROR : An application, form, schema, or table ID wasexpected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be thename of an application, a form or global function, a schema (or database,owner, or user), or a table:

An application name is required after the APPLICATION keywordin the master application form header

A form name is required after the FORM keyword in the standardform header.

A table name with an optional schema (or database, owner, oruser) name is required after the TARGET_TABLE keyword in theFORM section.

A global timer function name is required after the USING TIMERHANDLER clause of the CREATE TIMER EVENT statement.

A table name can be specified in either the table_name or

database_object .table_name format. The database_object argument isthe name of the database object that contains the table. This databaseobject is a database, owner, schema or user, depending on the RDBMS onwhich ACCELL/SQL is running.

Find the form script statement that is missing the application, form,table, or database, owner, schema, or user name. Also check for the useof variables that are not names. Rewrite the statement. See

for the syntax and usageof the form script statements.

Explanation

Correction

Explanation

Correction


40/273


8533 ACPL ERROR : A justification specification was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be a justification specification: CENTERED , LEFT , RIGHT , or a string. A justification specification follows the DISPLAY_JUSTIFY keyword inthe DISPLAY statement.

Find the DISPLAY statement that has the incorrect DISPLAY_JUSTIFY

clause. Omit the DISPLAY_JUSTIFY clause or follow theDISPLAY_JUSTIFY keyword by a valid justification specification. See

for the syntax and usageof the DISPLAY statement.

8539 ACPL ERROR : The NEXT keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theNEXT keyword. In a CHOOSE NEXT FORM statement, the NEXTkeyword must follow the CHOOSE keyword.

Find the CHOOSE NEXT FORM section that is missing the NEXTkeyword, and rewrite the statement. See

for the syntax and usage of the CHOOSE NEXTFORM section.

8541 ACPL ERROR : The RECORD keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theRECORD keyword. The RECORD keyword is required in theselocations:

after the CURRENT keyword in the DELETE CURRENTRECORD statement

after the CURRENT keyword in the UPDATE CURRENTRECORD statement

after the REJECT keyword in the REJECT RECORD statement

Because the compiler can not determine if a REJECT RECORD or aREJECT OPERATION statement was intended, error number 8620accompanies this error message.

Find the form script statement that is missing the RECORD keyword,

and rewrite the statement. See for the syntax and usage of form script statements.

Explanation

Correction

Explanation

Correction

Explanation

Correction


41/273


8543 ACPL ERROR : A table name was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be a tablename. A table name is required in these locations:

after the TARGET_TABLE keyword in a FORM section of astandard form

after an SLOCK , XLOCK or UNLOCK keyword in a lock statement

A table name can be specified in either the table_name ordatabase_object .table_name format. The database_object argument isthe name of the database object that contains the table. This databaseobject is a database, owner, schema, or user, depending on the RDBMSon which ACCELL/SQL is running.

Find the form script statement that is missing the table name, check thespelling of specified tables, and rewrite the statement. See

for the syntax and usageof form script statements.

8544 ACPL ERROR : The SELECT keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theSELECT keyword. In this case, the SELECT keyword must appear afterthe TO keyword in the SET statement.

Find the SET statement that is missing the SELECT keyword, andrewrite the statement. See for the syntax and usage of the SET and SELECT statements.

8545 ACPL ERROR : The SET keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theSET keyword. The SET keyword must appear after the ROW keyword inthe UPDATE SELECTED ROW statement.

Find the UPDATE SELECTED ROW statement that is missing the SET

keyword, and rewrite the statement. See for the syntax and usage of the UPDATE statement.

Explanation

Correction

Explanation

Correction

Explanation

Correction


42/273


8546 ACPL ERROR : An ACCELL/SQL type was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be a validACCELL/SQL type keyword. This message is displayed in these cases:

An invalid return type is specified in a declaration for a globalfunction.

An invalid type is specified for a target variable in the LOCALclause in the FORM section.

If the problem is in a global function declaration, make sure that thereturn type is specified by using one of the following keywords:

Use the ACCELL keyword in the EXTERN statement only if the functionis an ACCELL/SQL function. Use the C keyword for C functions and theSTORED keyword for SYBASE SQL Server stored procedures.

For a target variable in the LOCAL clause, make sure that the data type isspecified by using one of the following keywords:

8550 ACPL ERROR : The THEN keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theTHEN keyword. In this case, the THEN keyword must follow theexpression to be evaluated in the IF statement.

Find the IF statement with the missing THEN keyword and rewrite the

statement. See for thesyntax and usage for the IF statement.

Explanation

Correction

Explanation

Correction


43/273


8553 ACPL ERROR : The TO keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theTO keyword. The TO keyword is required in these locations:

after the ZOOM keyword in the DISABLE ZOOM statement

after the ZOOM keyword in the ENABLE ZOOM statement

(If the ENABLE ZOOM statement contains the optionalconsistency level clause, the keyword TO follows the consistencylevel clause.)

after the expression to be stored in the STORE statement

after the variable or variable list in the SET statement (Thevariable or variable list follows the SET keyword.)

after the ACTION , AUD_ACTION , FIND_ACTION , LABEL ,AUD_LABEL , FIND_LABEL , and KEYS keywords in the SETCOMMAND statement

Find the form script statement that is missing the TO keyword, andrewrite the statement. See for the syntax and usage of form script statements.

8554 ACPL ERROR : The TRIM keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theTRIM keyword. The TRIM keyword must follow the ERASE keyword inthe ERASE TRIM statement.

Find the ERASE TRIM statement that is missing the TRIM keyword, and

rewrite the statement. See for the syntax and usage of the ERASE TRIM statement.

8555 ACPL ERROR : The TX keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theTX keyword. The TX keyword must follow the CONTINUE , START , or

RESTART keyword in a consistency level clause of the CHOOSE NEXTFORM or CHOOSE FIRST FORM statement.

Explanation

Correction

Explanation

Correction

Explanation


44/273


This error message also occurs if no consistency level clause exists whensuch a clause is expected in a CHOOSE NEXT FORM or CHOOSEFIRST FORM section.

Find the CHOOSE NEXT FORM or CHOOSE FIRST FORM statementthat is missing the TX keyword, and rewrite the statement. See

for the syntax and usageof the CHOOSE NEXT FORM or CHOOSE FIRST FORM sections.

8556 ACPL ERROR : The UNTIL keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theUNTIL keyword. The UNTIL keyword must follow the statement list inthe REPEAT statement.

Find the REPEAT statement that is missing the UNTIL keyword, andrewrite the statement. See for the syntax and usage of the REPEAT statement.

8557 ACPL ERROR : The USING keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theUSING keyword. The USING keyword must appear in these locations:

following the consistency level clause of the CHOOSE NEXTFORM or CHOOSE FIRST FORM section or statement

following the SEC or SECONDS keyword of the CREATE TIMEREVENT statement

Find the form script statement that is missing the USING keyword, andrewrite the statement. See for the syntax and usage of the CHOOSE NEXT FORM and CHOOSEFIRST FORM sections or statements and the CREATE TIMER EVENTstatement.

Correction

Explanation

Correction

Explanation

Correction


45/273


8558 ACPL ERROR : A user name was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be adeveloper-defined name. A developer-defined name is required in thesecases:

for the function name after the FUNCTION keyword in adeveloper-defined function that is defined in the FUNCTIONsection

for the function parameters in the parameter list of adeveloper-defined function defined in the FUNCTION section

Find the FUNCTION section that is missing the developer-defined name,and rewrite the statement. See

for the syntax and usage of the FUNCTION section.

8560 ACPL ERROR : A variable was expected.The ACCELL/SQL compiler ( ACPL ) expected the next token to be avariable name. This error can occur wherever the grammar calls for avariable specification and one is not found.

Find the form script statement that has the missing or incorrect variablename. See for the syntaxand usage of form script statements.

8563 ACPL ERROR : The ZOOM keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theZOOM keyword. The ZOOM keyword is required in these locations:

after the ENABLE keyword in the ENABLE ZOOM statement

after the DISABLE keyword in the DISABLE ZOOM statement.

Find the ENABLE ZOOM or DISABLE ZOOM statement that is missingthe ZOOM keyword, and rewrite the statement. See

for the syntax and usage of these formscript statements.

8564 ACPL ERROR : There is not enough memory.

The ACCELL/SQL compiler ( ACPL ) tried to allocate memory for its

internal use and failed to allocate the memory. An internal compilerfunction found the failed memory allocation.

Explanation

Correction

Explanation

Correction

Explanation

Correction

Explanation


46/273


This error is not caused by a syntax error in your form script script.

Try one of the following solutions:

If the system did not have enough system memory or swap spaceavailable when you executed the compiler, try executing thecompiler again. This situation can occur on heavily loadedsystems.

If the compiler ran out of memory on a large form script script(over 1000 lines), try reducing the complexity of the form scriptscript. Create global form script functions to perform tasks that arerepeated.

If you still encounter memory allocation problems, call Unify CustomerSupport.

8565 ACPL ERROR : Cannot open file file_name .

The ACCELL/SQL compiler ( ACPL ) or some other ACCELL/SQL utility( program_name ) tried to open the file named file_name and failed. Thiserror occurs in the following cases:

ACPL was called with the y option and was unable to open thesymbol table output file.

ACPL was called with the c option and was unable to open thecode output file.

ACPL could not open the script file to be compiled. This case canoccur if you omit the a option (and the i option is not used)when trying to compile a master application script file.

Take these actions:

Make sure that you have write and execute permission on thecurrent directory.

Make sure you have read and write permission on the file beingopened.

Make sure that the operating system has enough resources (openfile descriptors and inodes) to open a new file.

Correction

Explanation

Correction


47/273


8566 ACPL ERROR : An illegal character was ignored.

The script file contained an ASCII character that the ACCELL/SQLcompiler ( ACPL ) could not interpret.

Search the script file for invalid or non-printable ASCII characters andremove them.

8567 ACPL ERROR : An ACCELL/SQL statement was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be thestart of a new form script statement. This error can occur in control flowstatements ( FOR , IF, REPEAT , WHILE , and SWITCH ), when thestatement being controlled by the control flow statement is not specified.

Find the form script control statement with the missing statement and besure to specify the statement under control of the control flow statement.See for the syntax andusage of the form script control statements.

8568 ACPL ERROR : An attribute was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be anattribute. When a variable name is followed by a colon ( :), the name of an attribute must follow the colon.

Find the form script statement that contains the incorrect variable name,and either remove the colon or add a valid attribute name. For thedescriptions of the ACCELL/SQL attributes, see

.

8569 ACPL ERROR : A form code section name was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to identifyan AFTER event or BEFORE event section such as BEFORE FORM ,

AFTER ZOOM , and so on. The second keyword must follow the AFTERkeyword or BEFORE keyword in one of the following event sections:

Explanation

Correction

Explanation

Correction

Explanation

Correction

Explanation


48/273


Find the AFTER or BEFORE section that is missing the second keyword,and rewrite the section. See

for the syntax and usage of event sections.

8573 ACPL ERROR : Either the KEY or VALUES keyword wasexpected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theKEY keyword. Either the KEY or the VALUES keyword must follow theRETURN keyword in the RETURN KEY clause of the ENABLE ZOOMstatement.

Find the ENABLE ZOOM statement that is missing the KEY or VALUESkeyword, and rewrite the statement. See

for the syntax and usage of the ENABLE ZOOMstatement.

8575 ACPL ERROR : The CASE or DEFAULT keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be eitherthe CASE or DEFAULT keyword. Either the CASE or DEFAULTkeyword must follow the BEGIN keyword in the SWITCH statement.

Find the SWITCH statement that is missing the CASE and DEFAULTkeywords, and rewrite the statement to use one of them. See

for the syntax and usageof the SWITCH statement.

8577 ACPL ERROR : The CHANGES keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be the

CHANGES keyword. The CHANGES keyword must follow the FIELDkeyword in the WHEN FIELD CHANGES section.

Correction

Explanation

Correction

Explanation

Correction

Explanation


49/273


Find the WHEN FIELD CHANGES section that is missing theCHANGES keyword, and rewrite the subsection. See

for the syntax and usage of the WHENFIELD CHANGES section.

8578 ACPL ERROR : There was an internal parser error.

This is an internal error and should not occur in the normal compiling of a form script.


8580 ACPL ERROR : There was a bad conversion.

TheACCELL/SQL

compiler (ACPL

) was unable to convert a characterstring representation of a constant to a constant type. This error occurs intwo cases:

ACPL ran out of memory.

ACPL found an internal conversion routine error.

If you suspect that ACPL has run out of memory, try reducing thecomplexity of the form script script. You can also create global formscript functions to perform tasks that are repeated.

If this error occurred because of an internal conversion routine error,please call Unify Customer Support.

8581 ACPL ERROR : There are too many symbol_type symbols.

As the ACCELL/SQL compiler ( ACPL ) processes a script file, it buildsthree internal tables to keep track of symbols. These tables are calledlocal , external , and ambiguous , each tracking a different symbol type.This error occurs if one of the tables runs out of space.

Reduce the complexity of the script by decreasing the number of variables in the symbol_type table. You can try creating global formscript functions to handle tasks which occur in several places. See

for more information about writingglobal form script functions.

Correction

Explanation

Correction

Explanation

Correction

Explanation

Correction


50/273


8582 ACPL ERROR : No free registers, the expression is too complex.

The ACCELL/SQL compiler ( ACPL ) ran out of internal registers as itattempted to convert a parsed expression into ACCELL/SQL code.Registers are used to store intermediate information. This error occurs if the compiler attempts to use more than 128 registers while it processesan expression.

Find the expression that is causing the error and reduce the complexity of this expression. Use ACCELL/SQL variables to hold intermediate valuesin the expression.

8583 ACPL ERROR : An attribute needs a variable name specified.

The ACCELL/SQL compiler ( ACPL ) found an attribute that has nocorresponding variable. An attribute must be preceded by a variable

name followed by a colon ( :). The name of an attribute must follow thecolon.

Find the form script statement that has the incorrect attribute name andeither remove the attribute or add a valid variable name. See

information about formscript attributes.

8584 ACPL ERROR : Too many errors, cant continue.The ACCELL/SQL compiler ( ACPL ) found the maximum number of errors (10) in the script file. The compiler does not stop processing ascript file when it finds the first error. Instead, ACPL attempts to check the whole file for errors. Once it found 10 errors, the compiler displaysthis error message and stops processing the script file.

Fix the syntax errors that have caused the existing error messages, and

then recompile the script file.

8585 ACPL ERROR : There is a bad system variable.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be asystem variable but found instead an invalid variable name.

Find the form script statement that has the incorrect system variable

name and correct the variable name. See for a list of form script system variables.

Explanation

Correction

Explanation

Correction

Explanation

Correction

Explanation

Correction


51/273


8587 ACPL ERROR : Table name not found in data dictionary.

The ACCELL/SQL compiler ( ACPL ) could not find information for adatabase table in the database. The compiler searches the database fortable information when compiling the TARGET_TABLE clause of theFORM section.

Find the form script statement that is causing the error and verify that thetable is defined in the current database, owner, schema, or user. Whetherthe table is contained in a database, owner, schema, or user depends onthe RDBMS on which ACCELl/SQL is running.

Correct the table name and substitute a valid table name. Also make surethat the database has not been corrupted. See

for the syntax and usage of the form scriptstatements.

8588 ACPL ERROR : No columns can be found.

The ACCELL/SQL compiler ( ACPL ) cannot find column information inthe database. The compiler searches the database for column informationin the following instances:

When processing a standard form, ACPL searches the database forinformation about the columns in the table specified by the theTARGET_TABLE clause of the FORM section.

Before writing the compiled form script to a file, ACPL searchesthe database for information about each local symbol that is atarget field.

Make sure that the target table in the current database design matches the

design you are using in the script. Verify that the database has not beencorrupted.

8590 ACPL ERROR : An expression was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be anexpression in a search ranges expression list. A search range expression

list contains search range values for a CLEAR_FIND_EXP targetattribute.

Explanation

Correction

Explanation

Correction

Explanation


52/273


Find the SET statement that sets the CLEAR_FIND_EXP target attribute,and rewrite the search ranges expression list so that each element in thislist begins with either an expression or the Clear-to-find expressionoperator ( =>).

See for the syntax andusage of the SET statement and forinformation about the Clear-to-Find expression operator.

8591 ACPL ERROR : The ACTION keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theACTION keyword. The compiler was looking for the ACTION keywordafter the NEXT keyword in the NEXT ACTION statement.

Find the NEXT ACTION statement that is missing the ACTIONkeyword, and rewrite the statement. See

for the syntax and usage of the NEXT ACTIONstatement.

8592 ACPL ERROR : The RECORD or FORM keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be eitherthe RECORD or FORM keyword. Either RECORD or FORM is requiredin these cases:

after the NEXT keyword in either an ON NEXT FORM or an ONNEXT RECORD event section

after the PREVIOUS keyword in either an ON PREVIOUS FORMor an ON PREVIOUS RECORD event section

Find the event section that is missing the RECORD or FORM keyword,and rewrite the section. See

for the syntax and usage of event sections.

8593 ACPL ERROR : The ADD or FIND keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be eitherthe ADD or FIND keyword.

Either ADD or FIND is required in the NEXT ACTION IS CLEAR TOADD or the NEXT ACTION IS CLEAR TO FIND statement. Because theTO keyword in these statements is optional, the ADD or FIND keyword

may follow the keyword CLEAR (if TO is omitted) or the keyword TO(if TO is included).

Correction

Explanation

Correction

Explanation

Correction

Explanation


53/273


Find the NEXT ACTION statement that is missing the ADD or FINDkeyword in the CLEAR TO clause, and rewrite the statement. See

for the syntax and usageof the NEXT ACTION statement.

8595 ACPL ERROR : The variable list doesnt match # of scalar_db_exps.

The ACCELL/SQL compiler ( ACPL ) found a SET statement that containsa variable list and a stored procedure call, but the stored procedure is notROW_VALUED . Before a stored procedure can be used in a SETstatement that contains a variable list, the stored procedure must bedeclared as ROW_VALUED in the EXTERN statement.

Find the SET statement and EXTERN statements that reference the storedprocedures and rewrite the appropriate statements. See

for the syntax and usage of the SET and

EXTERN statements.

8598 ACPL ERROR : The FIRST keyword was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be theFIRST keyword, after the CHOOSE keyword in the CHOOSE FIRSTFORM statement.

Find the CHOOSE FIRST FORM statement that is missing the FIRSTkeyword, and rewrite the statement. The CHOOSE FIRST FORMstatement can be used only in a master application form script. See

for the syntax and usageof the CHOOSE FIRST FORM statement.

8599 ACPL ERROR : Language section not valid in a Standard Form.

The ACCELL/SQL compiler ( ACPL ) found either the BEFOREAPPLICATION or the AFTER APPLICATION section in a standard formscript. These sections can appear only in a master application form script.

Find the BEFORE APPLICATION or AFTER APPLICATION section inthe standard form script, and remove it. Either move the section to themaster application form script, or find another valid section in a standardform script in which to execute the associated form script statements. See

for the syntax and usageof the BEFORE APPLICATION and AFTER APPLICATION sections.

Correction

Explanation

Correction

Explanation

Correction

Explanation

Correction


54/273


8600 ACPL ERROR : The CONSTANT expression was expected.

The ACCELL/SQL compiler ( ACPL ) expected the next token to be aconstant. The compiler expects a constant expression in these locations:

the value following the CASE keyword in the SWITCH statement

the row and column values in the BUTTON clause of the DEFINECOMMAND section

the label, action, and key strings in the DEFINE COMMANDsection

Find the SWITCH statement that is missing the constant in a CASEclause, and rewrite the statement. See

for the syntax and usage of the SWITCH statement.

8601 ACPL ERROR : More than one default expression in switchstatement.

The ACCELL/SQL compiler ( ACPL ) found more than one DEFAULTclause in a SWITCH statement.

Find the SWITCH statement that has the multiple DEFAULT clauses, andremove all but one of the DEFAULT clauses. See

for the syntax and usage of the SWITCHstatement.

8602 ACPL ERROR : There is an UNDEFINED function.

The ACCELL/SQL compiler ( ACPL ) found an undefined function. Thecompiler builds a table that contains information about alldeveloper-defined functions. This error occurs if the compiler cannot findan entry in this tables for a function called from a form script statement.

Find the form script statement that contains the undefined function name.Make sure the C-hook function is defined and declared, that it is spelledthe same way it has been defined, and that it is linked into the

application. See for moreinformation about writing C-hook functions.

Explanation

Correction

Explanation

Correction

Explanation

Correction


55/273


8603 ACPL ERROR : The number of parameters do not match.

The ACCELL/SQL compiler ( ACPL ) found a function or stored procedurecall that contains a different number of arguments from the number of parameters defined in the function or stored procedure definition.

Find the form script statement that has the function or stored procedure

call with the incorrect number of arguments. Make sure that you areusing the correct function or stored procedure name and the correctnumber of arguments in the function or stored procedure call.

8604 ACPL ERROR : A result parameter was expected.

The ACCELL/SQL compiler ( ACPL ) found a function or stored procedurecall that contains a constant argument when the compiler expected avariable. The compiler builds a table that contains information about alldeveloper-defined functions and stored procedures for the script. Thisinformation also indicates whether each parameter was declared as aRESULT parameter. A RESULT parameter requires a variable as anargument.

Find the form script statement that contains the function or storedprocedure call that contains the incorrect argument. Make sure that youare using the correct function or stored procedure name and theappropriate argument for each parameter. Use a variable for a RESULT orREFERENCE parameter and a constant or variable for a non- RESULTparameter.

8605 ACPL ERROR : A function was redeclared.

The ACCELL/SQL compiler ( ACPL ) found a declaration for a function orstored procedure that has already been declared in the script. Thefunction or stored procedure can be declared only once in the script.

Find the duplicate

unify error messages

Documents