Unify Error Messages

R
ACCELL/SQL:
Error Messages
E

)> #40-> 57657(9054 !(*7(3,495 (20-5740( #!
22 70./98 7,8,7;,+ 7049,+ 04 9/, #409,+ !9(9,8 5- 3,70*(
5 6(79 5- 9/08 +5*:3,49 3(> ), 7,675+:*,+ 97(483099,+ 97(48*70),+ 8957,+ 04 ( 7,970,;(2
8>89,3 57 97(482(9,+ 0495 (4> 2(4.:(., 57 *536:9,7 2(4.:(., 04 (4> -573 57 )> (4> 3,(48
,2,*97540* 3,*/(40*(2 3(.4,90* 5690*(2 */,30*(2 3(4:(2 57 59/,7<08, <09/5:9 9/, 67057 <7099,4
*548,49 5- #40-> 57657(9054
#40-> 57657(9054 3(1,8 45 7,67,8,49(90548 57 <(77(490,8 <09/ 7,86,*9 95 9/, *549,498 5- 9/08
+5*:3,49 (4+ 86,*0-0*(22> +08*2(038 (4> 03620,+ <(77(490,8 5- 3,7*/(49()0209> 57 -094,88 -57 (4>
6(790*:2(7 6:7658, :79/,7 #40-> 57657(9054 7,8,7;,8 9/, 70./9 95 7,;08, 9/08 +5*:3,49 (4+ 95
3(1, */(4.,8 -753 903, 95 903, 04 098 *549,49 <09/5:9 ),04. 5)20.(9,+ 95 4590-> (4> 6,7854 58:*/ 7,;080548 57 */(4.,8
"/, !5-9<(7, +,8*70),+ 04 9/08 +5*:3,49 08 -:7408/,+ :4+,7 ( !5-9<(7, 0*,48, .7,,3,49 "/,
!5-9<(7, 3(> ), :8,+ 57 *560,+ 542> 04 (**57+(4*, <09/ 9/, 9,738 5- 9/, 20*,48, (.7,,3,49 9 08
(.(0489 9/, 2(< 95 *56> 9/, !5-9<(7, 54 9(6, +081 57 (4> 59/,7 3,+0:3 -57 (4> 6:7658, 59/,7
9/(4 9/(9 +,8*70),+ 04 9/, 20*,48, (.7,,3,49
#40-> 57657(9054 ;(2:,8 (4+ (667,*0(9,8 (4> *533,498 >5: 3(> /(;, *54*,7404. 5:7 675+:*98 57 9/08
+5*:3,49 2,(8, (++7,88 *533,498 95
75+:*9 (4(.,7
#40-> 57657(9054
7,4( 5:2,;(7+ !9,
!(*7(3,495

&
#' $! (4+ 9/, #40-> 5.5 (7, 7,.089,7,+ 97(+,3(718 5- #40-> 57657(9054 #40->
(9(!,7;,7 08 ( 97(+,3(71 5- #40-> 57657(9054 #& 08 ( 7,.089,7,+ 97(+,3(71 5- 9/, 6,4 75:6 04 9/,
#409,+ !9(9,8 (4+ 59/,7 *5:4970,8 "/, & %04+5< !>89,3 08 ( 675+:*9 5- 9/, (88(*/:8,998 48909:9, 5",*/4525.> 590- ! (4+ !590- (7, 97(+,3(718 5- 6,4 !5-9<(7, 5:4+(9054 4* !'! 08 (
7,.089,7,+ 97(+,3(71 (4+ ! !,7;,7 @0)7(7> (4+ 6,4 !,7;,7 (7, 97(+,3(718 5- !>)(8, 4*
& 08 ( 7,.089,7,+ 97(+,3(71 5- 4-5730= !5-9<(7, 4* ( 8:)80+0(7> 5- ! 08 (
97(+,3(71 5- 536:9,7 885*0(9,8 49,74(9054(2 4* 08 ( 7,.089,7,+ 97(+,3(71 5- 7(*2,
57657(9054 !:4 08 ( 7,.089,7,+ 97(+,3(71 (4+ !:4$0,< !:4@
!:4@ &,%! !:4! @! (4+
6,4 %04+5<8 (7, 97(+,3(718 5- !:4 0*758>89,38 22 ! 97(+,3(718 (7, 97(+,3(718 57 7,.089,7,+
97(+,3(718 5- ! 49,74(9054(2 4* ! 89(9054 08 20*,48,+ ,=*2:80;,2> 95 !:4 0*758>89,38 4*
5;,22 08 ( 7,.089,7,+ 97(+,3(71 5- 5;,22 4* (*04958/ 08 ( 97(+,3(71 5- 662, 536:9,7 4*
0*7585-9 ! !@! (4+ %04+5<8 (7, 7,.089,7,+ 97(+,3(718 5- 0*7585-9 57657(9054 22 59/,7
675+:*98 57 8,7;0*,8 3,49054,+ /,7,04 3(> ), 7,.089,7,+ 97(+,3(718 97(+,3(718 57 8,7;0*, 3(718 5- 9/,07
7,86,*90;, 3(4:-(*9:7,78 *536(40,8 57 57.(40?(90548
(79 :3),7
Contents
About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error Message Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ACCELL/SQL Combiner (ACMB) Error Messages . . . . . . . . . . . . . . . .
ACCELL/SQL Linker (ALNK) Error Messages . . . . . . . . . . . . . . . . . . .
16
ACCELL/SQL Compiler (ACPL) Error Messages . . . . . . . . . . . . . . . . .
24
ACCELL/Manager (AMGR) Error Messages . . . . . . . . . . . . . . . . . . . . .
87
ACCELL/SQL Interactive Debugger Error Messages . . . . . . . . . . . . . .
129
ACCELL/Manager Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . .
133
ACCELL/Generator (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

describes the messages that may be
displayed while you are using ACCELL/SQL . Each message description
includes the message text and number, the possible causes, and solutions.
Graphic
Conventions
This manual uses various graphic conventions to help you easily

distinguish 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 terminal
screen are represented in a screen outline, for example:
COMPANY:
ADDRESS:
CITY:
MAIN PHONE:
CONTACT:
SALES REP#:
NAME:
PHONE:
STATE:
ZIP:
MAP:
Item Names
References to program names, database table and column names, screen
form names, and form field names appear in bold typeface, for example:
To define a form, you fill in the Form Definition form with the
appropriate information.
You use the same procedure to define the address_1 and
address_2 fields that you used to define the co_name field.
The Target Table field lets you specify which database table this
form will directly query and update.
5
Keyboard Keys
A word or letter framed to look like a key indicates the corresponding
key on your keyboard, for example:
RETURN
Represents the return key. This key could be labeled as

Enter, RTN, or .
ACCELL/SQL Commands
A word or words that appear in bold, italic, sans serif typeface indicates
an 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 , you
can assign commands such as to different function
keys, for instance F3 .
Syntax
Conventions
This manual uses the following syntax conventions to describe the

format of ACCELL/SQL statements and functions, RPT statements, and
operating system command-level commands:
boldface
Boldface words are command keywords or literal strings

that you must type exactly as shown.
italic words
Italic words indicate words, variables, numbers, or

expressions that you must provide. Examples are table
names, column names, and constants.
Italic words are also used for manual names and terms
defined in the glossary. All-uppercase italics are used for
configuration variable names.
UPPERCASE
UPPERCASE words are ACCELL/SQL keywords.

ACCELL/SQL keywords are not case sensitive: you can
type either uppercase or lowercase letters.

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

($). The dollar sign distinguishes an ACCELL/4GL
function from a user-defined function. Do not include
use a dollar sign when you call your own functions.
Other
Conventions
[]
Non-bold square brackets indicate that the enclosed word

or item is optional and may be left out. Boldface
brackets, [ ], are syntax elements that must be included,
as in count[character].
||
Vertical bars that enclose a stacked list of options mean

that you can choose one of the listed options, but only
one of them.
...
Ellipsis points indicate that you may repeat the

immediately preceding item any number of times, as
needed.
The manual also uses the following symbols to indicate special types of
information:
Tip
Tip contains helpful information.
Warning
Warning cautions against actions that could cause data loss or damage to
the data base.
Additional Help
Additional Help tells you where to find more information about
described topics.
Error Message Descriptions
Chapter
Focus
The ACCELL/SQL error messages that are described in this manual are
grouped by category: compiler, linker, ACCELL/ Manager, and so on.
Error message descriptions include the text of the error message, an
explanation of the probable cause, and suggestions for correcting the
problem. Each error message entry has this format:

-8317

ACMB ERROR: Type conflict on target variable .

The error message number corresponds to the number of the error

message text in the ACCELL/SQL message file, $UNIFY/unify.msg.
On-screen, the error message number is displayed in parentheses at the
end of the error message text or in the upper right corner of the error
form 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 markers
are replaced by actual string or numeric values that apply to the
individual error condition. For example, in message 8317 the
substitution 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 Index
on page NO TAG to obtain the number. Alphabetic Index lists the
ACCELL/SQL error messages alphabetically by error message text.
If you follow the instructions in the suggested correction and are still
unable to resolve the error, please call Customer Support for assistance.
Make sure that you have the error message number available when
calling.
10
Error Message Descriptions
ACCELL/SQL Combiner (ACMB) Error

Messages
The following messages may be displayed while you are combining an
ACCELL/SQL application.
8201
Explanation
SAR ERROR: There is a corrupt archive file archive_name.
This error indicates that a recently created archive file was successfully
created. However, the archive was corrupt when the ACCELL/SQL
combiner, ACMB, attempted to read the archive.
This error can occur in these cases:
The application directory does not contain enough disk space to
create the archive file, and no error status was returned by the
operation system.
The newly create archive file was modified by some outside
source before ACMB read the file.
Correction
Make sure that the application directory contains enough disk space, then
rebuild the archive by using ACMB or ACCELL/E nvironment.
8205
SAR ERROR: Cannot open archive_name, error number os_error.
Explanation
The ACCELL/SQL combiner (ACMB) could not open the archive file
named archive_name, in the current directory. This archive file can be
either 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.
Correction
Make sure that you have read and write permission in the current
directory and that the current directory has enough space to create a new
archive file.
8206
SAR ERROR: Cannot create archive_name, error number os_error.
Explanation
The ACCELL/SQL combiner (ACMB) could not create the archive file
named archive_name in the current directory. This archive file can be
either a new archive file or a temporary archive file.
ACCELL/SQL Combiner (ACMB) Error Messages
11
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.
Correction
8207
Explanation
directory and that the current directory has enough space to create a new
archive file.
SAR ERROR: Cannot close archive name, error number os_error.
The ACCELL/SQL combiner (ACMB) failed to close the temporary

archive named archive name, which was created to build a new archive.
This error can occur when the host operating system has a problem or the
combiner 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.
Correction
8208
Explanation
Correction
8209
Explanation
Correction
8210
Explanation
Correction
12
If this error persists, contact Unify Customer Support.

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.
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.
SAR ERROR: Error renaming file_name to file_name.
The combiner was unable to rename a file to the specified file name after
creating a new archive in a temporary file.
Make sure that the archive files and directories have the correct
permissions and sufficient space. If the problem persists, remove the
archive and rebuild the application.
8300
Explanation
ACMB ERROR: There was an error in reading the file file_name.
The ACCELL/SQL combiner (ACMB) cannot read an ACCELL/SQL form

file (a .fq or .aq file) and the form is not a global function, or the
combiner 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 file
does not exist, or you do not have read and write permission for
the file.
The .fq or .aq file can be opened, but the file is corrupted.
The maximum number of file descriptors allowed for a process has
been reached.
The system is out of memory.
Correction
Make sure that the file exists and that you have read and write
permission 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.
Tip
If your system is configured with the minimum memory requirements for
ACCELL/SQL or you are running on a heavily loaded system, ACMB can
fail to allocate the memory needed to combine both form and object
code. 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
Explanation
ACMB ERROR: There was a bad magic number.
The ACCELL/SQL combiner (ACMB) has encountered an unknown

magic number in an ACCELL/SQL file. Every ACCELL/SQL file type has
an associated magic number that enables executables to distinguish
between different types of files.
13
This error can occur in these cases:

The combiner has been asked to open a file that is not an archive
file.
The file may have been corrupted by some system or program
failure.
The user has made an execution error.
Correction
8302
Explanation
Make sure that you have specified the correct archive file name. Try
removing the archive file and running ACMB again.
ACMB ERROR: The Combine failed in malloc memory.
The ACCELL/SQL combiner (ACMB) has run out of memory while

trying to combine the form file and optional object file. This error can
occur when ACMB is combining forms with a large number of screen
fields (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) are
represented by a structure referred to as a form unit. An ACCELL/SQL
archive 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 the
form unit)
code space (all ACCELL/4GL statements in the .ao or .fo file, plus
the object code that is generated automatically by the generator
when 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 space
available at the time you ran the combiner. This situation can occur on
heavily loaded systems.
Correction
14
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 insufficiency
was a temporary condition at execution time, try running the combiner
again.
8303
Explanation
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 each
field in the list.
The ACCELL/SQL combiner (ACMB) creates a temporary file that
contains information for a form from the .fq/.fo, or .aq/.ao file pair. One
of the steps in creating this file is to change the initial NEXT_FIELD
attribute for each field in the list so that it indexes the symbol table built
from information in the .fo/.ao and .fq/.aq files.
This error occurs when the combiner cannot find a symbol table entry for
a field in the list created by the generator.
Correction
8304
Make sure that no statement that sets the NEXT_FIELD attribute sets the
attribute to a non-existent field.
ACMB ERROR: Checksum error. Verify .fs and .fq target table
names match.
Explanation
When the ACCELL/SQL combiner (ACMB) is processing a form that has

a form script, it verifies that the checksum stored in the script file
matches the checksum in the form file. This error can occur in these
cases:
Either the script file contains a target table name that is not in the
form file, or the form file contains a target name that is not in the
script file.
The database design was changed, and one of the files has not
been rebuilt; that is, this file is out of date.
Correction
Make sure the target table name is the same for both the form file named
on the Form Definition form and the script file named in the FORM
section.
If the error persists, run the form file first through Q2ASC then through
ASC2Q to recompute the checksum; or edit the form file with the
generator to achieve the same result. To recompute the checksum for the
object file, recompile the object file with ACPL.
15
Even if the script file does not refer to a database column that has been
added to the target table, the file must still be recompiled so that its
checksum can be calculated according to the updated database design.
8305
Explanation
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, it

creates a list of all screen fields that are referenced by the script and
stores 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 the
form.
When the ACCELL/SQL combiner (ACMB) combines a form and its form
script, it verifies that each field listed in the script is actually in the form
file. 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 FIELD
section that lists an invalid field.
Correction
8306
Explanation
Verify the spelling of the field names listed in the FIELD sections and in
statements that reference fields. Also make sure that you have defined the
field name that you are using.
ACMB ERROR: There was a form name mismatch.

a form script, ACMB makes sure that the form or application name stored
in the object (.fo/.ao) file matches the form or application name stored in
the form file (.fq/.aq).
This error occurs if the combiner discovers an inconsistency.
Correction
If you are combining a standard form file and form script file, make sure
the FORM section in the form script file lists the same form name as
specified on the ACCELL/SQL generator Form Definition form for the
standard 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 the
same application name as specified on the ACCELL/SQL generator Form
Definition form for the master application form.
16
8307
ACMB ERROR: There was a form/application mismatch.
Explanation

a form script, ACMB makes sure that the form file (.fq/.aq) and the
corresponding object file (.fo/.ao) both specify the same type of form
(master application or standard). This error occurs if the combiner
discovers an inconsistency.
Correction
Make sure that both the form file and the form script file are for the same
type of form: standard or master application.
8308
Explanation
Correction
8309
Explanation
ACMB ERROR: There is a corrupt file.
The ACCELL/SQL combiner (ACMB) cannot read all or part of the

archive index for an ACCELL/SQL archive file (.fa file).
Delete the existing archive file (.fa) and rebuild it with ACMB. For
information on how to use ACMB to build an archive file, see the ACMB
syntax and usage description in

.
ACMB ERROR: There was an error in adding the form.
The ACCELL/SQL combiner (ACMB) cannot write a form unit in an

ACCELL/SQL archive file.
This error can occur in one of these cases:
The combiner cannot add a new form unit. The combiner creates a
new 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 the
archive file. The attempt to create the temporary archive file failed.
17
The combiner cannot add the form unit (either a pre-existing form
unit or the new form unit stored in a temporary file) to an existing
application archive file. The combiner reads in the existing form
units in the archive file, sorts them with the form unit for the form
to be added to the archive, then writes all the form units to the
archive file.
Correction
8310
Explanation
Make sure that you have permission to write in the current directory and
that the directory contains enough space for a temporary copy of the
archive, plus a temporary copy of the combined form and code file. Also,
if you are using the UNIX operating system, make sure that your ulimit
is set high enough to allow the creation of the archive file.
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 error
occurs if the combiner encounters a duplicate form name.
Correction
8311
Explanation
Correction
18
Search the application directory for any form script files or form files
that may contain duplicate form names. The form name in a form script
is listed in the FORM section. The form name in a form file is listed on
the ACCELL/G enerator Form Definition form for the form.
ACMB ERROR: There was an error in reading the form.
Once the ACCELL/SQL combiner (ACMB) has produced the temporary

file of information from the forms .fo/.fq or .ao/.aq file pair, it either
merges this information into the existing archive file or creates a new
archive file. This error occurs when the combiner is unable to merge the
temporary file information into the existing archive file. To create the
new archive, the combiner must be able to read the old archive entries in
the 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.
8312
ACMB ERROR: Warning: there was an illegal display variable
name: variable_name.
Explanation
Correction
8313
Explanation
Screen field names of the form fkey_prompt_nn (where nn is a

number) are system variables that define ACCELL/SQL function key
prompts. The function key number, indicated by nn, must fall between 0
and 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 and
99.
ACMB ERROR: There was an error opening file_name, error

number 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 no
more internal file descriptors, or an operating system error.
Correction
Take corrective action based on the os_error number provided:

If os_error is 11, see your system administrator about
reconfiguring 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. In
this case, the archive must be recreated from scratch. For information
about using the ACMB utility, see

.
19
8314
ACMB ERROR: There was an error renaming temp_archive_name to
existing_archive_name.
Explanation
The ACCELL/SQL combiner (ACMB) was unable to rename the

temporary file to the name of the existing archive file. The combiner
creates 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.
Correction
Make sure that you have read and write permissions in the current
directory.
8315
ACMB ERROR: There was an error creating file_name, error
number os_error.
Explanation
Correction
8316
The ACCELL/SQL combiner (ACMB) could not create the temporary file
to 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. Consult
your system error file for a list of valid error numbers.
Make sure that you have read and write permissions in the current
directory.
ACMB ERROR: There was an error closing a file, error number
os_error.
Explanation
Correction
20
The ACCELL/SQL combiner (ACMB) could not close the temporary file
used 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 internal
error and should not occur in the normal execution of ACMB.
If this error occurs, please call Unify Customer Support.
8317
Explanation
Correction
8318
ACMB ERROR: Type conflict on target variable variable_name.
On certain RDBMS products, the data types of target ACCELL/SQL

variables can be chosen by the developer in the generator or in a form
script file. This error indicates that the specified data types are
incompatible between the generator and compiler or between
ACCELL/SQL and the database.
Make sure that the data types specified for target variables in the
generator and compiler are compatible with each other and with the
RDBMS data type of the target column.
ACMB ERROR: The DBTYPE configuration variable is not set or is
set incorrectly.
Explanation
ACCELL/SQL could not access its own information about the current
database product it is to interface with. This error should not normally

occur.
Correction
8319
Explanation
Correction
8320
Explanation
Correction
Make sure that the DBTYPE configuration variable is set correctly. If it is,
please contact Unify Customer Support.
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 no
target table was specified when the corresponding form was generated.
Remove the TARGET_TABLE clause from the form script FORM
header, or regenerate the form and add the appropriate target table on the
Form Definition form.
ACMB ERROR: table name used as target table in AGEN, no target
table in 4GL.
A target table was specified on the Form Definition form in

ACCELL/G enertor, but no TARGET_TABLE clause was used in the form
script FORM header of the corresponding form script.
Add a TARGET_TABLE clause to the form script FORM header, or
regenerate the form and remove the target table specified on the Form
Definition form.
21
8321
ACMB ERROR: table name used as target table in AGEN,
table_name used as target table in 4GL.

Explanation
The target table specified on the Form Definition form is different from
the table specified in the TARGET_TABLE clause of the form script
FORM header.
Correction
After determining the correct target table for the form, modify the target
table name on the Form Definition form, or change the table name
specified in the TARGET_TABLE clause of the form script FORM
header.
8322
ACMB ERROR: Number of target columns known to .fq and .fo for
table table name do not match.
Explanation
Between the time ACCELL/G enerator was run and the compiler was run
the number of columns in the specified table have changed.
Correction
Rerun ACCELL/G enerator on the screen form (.fq file) and recompile the
form script (.fs file). Then rerun the combiner.
8323
ACMB ERROR: Columns in target table table name for .fq and .fo
differ.
Explanation
the names of some of the columns in the specified table have changed.
Correction
After removing obsolete columns, rerun ACCELL/G enerator on the

screen form (.fq file) and recompile the form script (.fs file). Then rerun
the combiner.
Warning
If the original form contains target fields that are no longer in the
target table, ACCELL/Genertor changes these fields to non-target
screen fields.
22
8324
ACMB ERROR: The characteristics of column column name are
different in the .fq and .fo.

Explanation
the characteristics of some of the columns in the specified table have
changed.
Correction
Rerun ACCELL/G enerator on the screen form (.fq file) and recompile the
form script (.fs file). Then rerun the combiner.
Warning
If the original form contains target fields for columns that have
changed, ACCELL/Generator changes these fields to match the
database definitions.
8325
Explanation
ACMB ERROR: There was a class mismatch for field field_name.
The dimensions of an array were specified differently in

ACCELL/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 through

ACCELL/G enerator and in an ACCELL/4GL form script.
Correction
8326
Explanation
Correction
Make sure that the dimensions of the arrays defined in

ACCELL/G enerator match the dimensions specified for the same arrays in
ACCELL/4GL form scripts.
ACMB ERROR: The local array array_name was not defined.
A symbol that is local to the form being combined was referenced as an

array in an ACCELL/4GL form script, but the array was not defined as
local in the ACCELL/4GL form script or in ACCELL/G enerator.
Locate the reference and change it to reference an existing array, or
define the array that is being referenced. Arrays can be defined in
ACCELL/G enerator or in an ACCELL/4GL form script.
23
ACCELL/SQL Linker (ALNK) Error

Messages
8401
ALNK ERROR: The application linker does not have enough
memory.
Explanation
The ACCELL/SQL linker (ALNK) tries to read information from the

appropriate archive file for each application form. This error occurs when
the linker is unable to allocate space in which to read the information and
indicates 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 the
linker.
You have a large number of form units (over 100) in the same
archive 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 an
ACCELL/SQL archive file (.fa file) as a collection of form units.
Correction
8402
Explanation
Correction
If you suspect that not enough system memory was available at the time
you executed the linker, try executing the linker again before trying to
split the archive file. If you have a large number of form unit in the
same archive file, try splitting that archive into two archives.
ALNK ERROR: There is a duplicate required form form_name in
the application.
The ACCELL/SQL linker (ALNK) sets up an internal table containing

information about all application forms, including global functions. This
error occurs if the linker finds a duplicate entry for a required form in the
internal table.
Make sure that the REQUIRED FORMS and REQUIRED FUNCTIONS
clauses of the APPLICATION section in the master application form
script contain no duplicate form or function names.
The application form is not treated as a required form. Therefore, the
REQUIRED FORMS section may list a form that has the same name as
the application.
24
ACCELL/SQL Linker (ALNK) Error Messages
8404
ALNK ERROR: Form form_name is not in the archive or the archive
doesnt exist.
Explanation
The form or function was listed in the REQUIRED FORMS or

REQUIRED FUNCTIONS clause. However, the ACCELL/SQL linker
(ALNK) could not find the form_name form or function in the default
archive or any of the archives listed in the ARCHIVES clause of the
APPLICATION section in the master application script. Either the
archive could not be found or the form_name form or function was not
archived.
Correction
Take these steps:

1. Make sure that the form_name form or function is spelled
correctly and is listed in the REQUIRED FORMS or REQUIRED
FUNCTIONS clause in the APPLICATION section for the master
application 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).
If the
clause is not correct, edit the clause,
recompile ( ) the master application script, recombine
( ) the master application form, and relink the
application.
If the
clause is correct, try archiving the
indicated form or function again.
8405
Explanation
ALNK ERROR: Error opening application archive file

archive_name, Status = status_value.
The ACCELL/SQL linker (ALNK) was unable to open the archive file (.fa
file), archive_name. This error can occur in these cases:
A misspelled or otherwise invalid archive file name has been
specified in the REQUIRED FORMS section of the master
application form script. The archive name must include the .fa file
name suffix.
The person who is trying to link the application does not have
write permissions on the archive.
25
The archive file cannot be opened.

The archive file is corrupted.
The maximum number of file descriptors allowed per process has
been reached.
The status status_value indicates the cause of the failure. Status is set to
one of these values:
an operating system error number, if the archive cannot be opened
or is corrupted
11, if the number of file descriptors has been exceeded
2, if the archive file header was corrupted
Correction
Try one of these solutions:

Make sure that the archive name is specified correctly in the
master application form script.
Make sure that you have read and write permissions on the archive
file archive_name.
If the file permissions are correct, the archive is probably
corrupted. Delete the existing archive file (.fa) and rebuild it with
ACMB. For information on how to build an archive file, see the
ACMB description in
.
If status_value is 11, see your system administrator about
reconfiguring your operating system with more file descriptors.
8406
ALNK ERROR: Ran out of memory while allocating archive index
space.
Explanation
Correction
The ACCELL/SQL linker (ALNK) ran out of memory while trying to read
in 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 master
application form APPLICATION section.
3. Recombine (ACMB) the archive and relink (ALNK) the
application. For information about building an archive file, see the
ACMB description in
.
26
8407
ALNK ERROR: There was an error reading an archive index, Status
= os_error.
Explanation
The ACCELL/SQL linker (ALNK) was unable to read in the archive index
for an archive file (.fa file). Status os_error is the error number returned
by the operating system.
Correction
Rebuild the archive file with ACMB. For information about building an
archive file, see the ACMB description in

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

Explanation
Correction
8409
The ACCELL/SQL linker (ALNK) was unable to find an entry in the

archive file with an application name matching the application name
specified in the command line. The linker searches the archive file (.fa
file) specified in the command line for this application entry.
Make sure the application name and archive name specified in the ALNK
command line are spelled correctly. Recombine the master application
form with ACMB and relink the application. For information on how to
combine the master application form, see the ACMB description in

.
ALNK ERROR: Error closing an application archive file, Status =
os_error.
Explanation
Correction
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 file
was reached. Otherwise, os_error is the status returned by the operating
system.
If you receive this error, please call Unify Customer Support.
27
8410
ALNK ERROR: There was an error while reading a form file, Status
= status_value.
Explanation
Correction
The ACCELL/SQL linker (ALNK) cannot read the archive file. The
archive file is probably corrupted. If not enough system memory is
available, the status status_value is 5. Otherwise status_value is set to
the error number returned by the operating system.
A status_value of 5 can occur on a heavily loaded system. If your
system 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 ACMB
description in

.
8411
Explanation
ALNK ERROR: Ran out of archive name space.
The ACCELL/SQL linker (ALNK) keeps an internal table of all the

archive files that are used by the application. This error can occur while
the 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.
Correction
28
If you are using more than 512 archives in the application, reduce the
number of archives being used. If you are running the linker on a heavily
loaded system, try running the linker again when the system load is
lighter.
8413
ALNK ERROR: ALNK : BAD Exit Status = error_number.
Explanation
The ACCELL/SQL linker (ALNK) encountered an error while attempting

to link the application. This is a general error message and is usually
preceded by another more specific message that indicates why the linker
failed. Status error_number is the message number of the more specific
error message.
Correction
Check the preceding error messages for a more complete description of

the error. Use these preceding messages and the status value to determine
the cause of the error.
8414
Explanation
Correction
8415
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 the
archive files, it tries to create or open the application map file. This error
occurs if the linker cannot open or create the file.
Make sure that you have read and write permissions for the application
directory that contains the application map file (.al). Verify that the
application directory contains enough space to hold the new (.al) file.
ALNK ERROR: There was an error while closing the .al file, Status =
os_error.
Explanation
Correction
8416
The ACCELL/SQL linker (ALNK) was unable to close the newly created
application file. The status os_error is the error number returned by the
operating system. This is an internal error and should not occur in the
normal linking of an ACCELL/SQL application.
ALNK ERROR: There was an error while seeking or writing the .al
file.
Explanation
The ACCELL/SQL linker (ALNK) found a corrupted application map file

(.al file).
Correction
Delete the application map file (.al) and execute ALNK again to recreate
this file.
29
8418
ALNK ERROR: Could not find the form_name form in the
archive_name archive.
Explanation
Correction
8419
Explanation
Correction
8420
The ACCELL/SQL linker (ALNK) cannot find an entry for the form_name
form or function in the archive archive_name. For each form or function
listed 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 the
archive name in the REQUIRED FORMS or REQUIRED FUNCTIONS
clause of the APPLICATION section are correct. Recombine the
form_name form or function in the archive archive_name by using
ACMB. For information about building an archive file, see the ACMB
description in

.
ALNK ERROR: Ran out of archive names getting checksums.
This is an internal error and should not occur in the normal linking of an
ALNK WARNING: Form form_name could not be found in an
archive.
Explanation
30
The ACCELL/SQL linker could not find the form form_name in the
default archive or any of the archives listed in the ARCHIVES clause of
the APPLICATION section in the master application form script. This is
simply a warning message. The form form_name was not specified in a
REQUIRED FORMS clause but was referenced by a form in the
application.
Correction
Take these actions:

If the form will not be accessed at runtime (the path of the
application 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 archive
containing it is listed in the ARCHIVES clause or make sure that
the form and its archive is specified in the REQUIRED FORMS
clause.
Make sure that the archive exists in the current directory or in the
directory indicated by the ACLPATH configuration variable).
If the ARCHIVES or the REQUIRED FORMS clause is not
correct, edit the clause, recompile (ACPL) the master application
script, recombine (ACMB) the master application form, and relink
the application.
If the master application script is correct, try archiving the
indicated form again.
31
ACCELL/SQL Compiler (ACPL) Error

Messages
8501
Explanation
ACPL ERROR: A ( operator was expected.
The ACCELL/SQL compiler (ACPL) expected a left parenthesis, (, in a

form 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 any
arguments in a function call or stored procedure call (The
parentheses are required even if the function or stored procedure
has no arguments.)
after the function name and before any function parameters in a
FUNCTION statement: either a local or global function
declaration. (The parentheses are required even if the function has
no parameters.)
in an AT clause before the row and column coordinates (The AT
clause can appear in the DISPLAY, ENABLE ZOOM , DISPLAY
TRIM, and ERASE TRIM statements, and, for GUI options, in the
BUTTON LOCATION clause of the DEFINE COMMAND
statement.)
Correction
8502
Explanation
32
Find the form script statement that is missing the parenthesis, and rewrite
the statement. See the

for
the syntax and usage of form script statements and sections.
ACPL ERROR: A ) operator was expected.
The ACCELL/SQL compiler (ACPL) expected a right parenthesis, ), in

a form script statement or section.
ACCELL/SQL Compiler (ACPL) Error Messages
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 (The
parentheses are required even if the function or stored procedure
has no arguments.)
after the function parameters in a FUNCTION statement: either a
local or global function declaration (The parentheses are required
even if the function has no parameters.)
in an AT clause after the row and column coordinates (The AT
clause can appear in the DISPLAY, ENABLE ZOOM , DISPLAY
TRIM, and ERASE TRIM statements, and, for GUI options, in the
BUTTON LOCATION clause of the DEFINE COMMAND
statement.)
at the end of an expression that is introduced by a left parenthesis,
(
Correction
8503
Explanation
Find the form script statement that is missing the right parenthesis, and
rewrite the statement. See the

for the syntax and usage of form script statements and
sections.
ACPL ERROR: A , was expected.
The ACCELL/SQL compiler (ACPL) expected a comma (,) in a form

script statement.
The comma is required in these locations:
in the AT position clause between the row and column
coordinates. (The AT clause can appear in the DISPLAY, ENABLE
ZOOM , DISPLAY TRIM, and ERASE TRIM statements, and, for
GUI options, in the BUTTON LOCATION clause of the DEFINE
COMMAND statement.)
in the MATRIX declaration between the row and column
specifications
between parameters in a function definition
Correction
Find the form script statement that is missing the comma, and rewrite the
statement. See the

for the
syntax and usage of form script statements and sections.
33
8504
ACPL ERROR: A form or function name exceeded 15 characters in
length.
Explanation
You have specified more characters than allowed for a form or function
name. 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 44
characters long.
Stored procedure names can be up to 44 characters long if allowed by
the RDBMS. If the RDBMS limits stored procedure names to fewer
than 44 characters, ACCELL/SQL allows the RDBMS limit. If the
RDBMS allows stored procedure names to be more than 44 characters,
ACCELL/SQL uses the 44-character limit.
Correction
8505
Explanation
Make sure that form names and global function names are 15 characters
or less. Make sure that local function names and C-hook function names
are 44 characters or less. Make sure that stored procedure names are 44
characters or less and not more than the number of characters allowed by
the RDBMS.
ACPL ERROR: A : was expected.
The ACCELL/SQL compiler (ACPL) expected a colon (:) in a form

script statement.
The colon is required in these locations:
after the constant specified in a CASE clause of a SWITCH
statement
after the command name in the SET COMMAND statement
after the DEFAULT keyword in a SWITCH statement
Correction
34
Find the form script statement that is missing the colon, and rewrite the
statement. See the

for the
syntax and usage of form script statements and sections.
8506
Explanation
ACPL ERROR: A ; was expected.
The ACCELL/SQL compiler (ACPL) expected a semicolon (;) in a form

script 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 the
loop in a FOR statement (The semicolon is required even if no
expression is specified.)
after the expression to be evaluated at the beginning of each loop
iteration in a FOR statement (The semicolon is required even if no
expression is specified.)
Correction
8512
Explanation
Find the form script statement that is missing the semicolon and rewrite
the statement. See the

for
the syntax and usage of the DELETE SELECTED ROW, FOR, SLOCK,
UNLOCK, and XLOCK statements.
ACPL ERROR: The BEGIN keyword was expected.
The ACCELL/SQL compiler (ACPL) expected the next token to be the

BEGIN keyword. The BEGIN keyword is required in these locations:
before the statements in an EXECUTING clause of the SELECT
statement
after the expression following the SWITCH keyword in a
SWITCH statement
Correction
Find the form script statement that is missing the BEGIN keyword and

for the syntax and usage of form script statements.
35
8517
Explanation
ACPL ERROR: The END keyword was expected.

END keyword. The END keyword is required in these locations:
after the statements in an EXECUTING clause of the SELECT
statement
at the end of a SWITCH statement
Correction
8518
Explanation
Find the form script statement that is missing the END keyword, and

ACPL ERROR: The FIELD keyword was expected.

FIELD keyword. The FIELD keyword is required in these locations:
after the RESTART ON keywords in a RESTART ON FIELD
statement
after the WHEN keyword in a WHEN FIELD CHANGES
subsection
after the INIT keyword in an INIT FIELD subsection
Correction
8520
Explanation
Find the form script statement or section that is missing the FIELD
keyword, and rewrite the statement or section. See the

for the syntax and usage of form script
statements and sections.
ACPL ERROR: The FORM keyword was expected.

FORM 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
Correction
36
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.
8522
ACPL ERROR: The FROM keyword was expected.
Explanation

FROM keyword. The FROM keyword must follow the variable name in
the RETRIEVE statement.
Correction
Find the RETRIEVE statement that is missing the FROM keyword, and
rewrite the statement. See

for the syntax and usage of the RETRIEVE statement.
8523
ACPL ERROR: The FUNCTION keyword was expected.
Explanation

FUNCTION keyword. The FUNCTION keyword must follow the return
type in either a global or a local function declaration.
Correction
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.
Explanation

name of a field variable or a target field variable. A field variable name
or target field variable name must be specified in a FIELD section.
Correction
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. Rewrite
the statement or section. See

for the syntax and usage for form script statements and
sections.
8525
ACPL ERROR: A file ID was expected.
Explanation
The ACCELL/SQL compiler (ACPL) expected the next token to be an

operating system file name, which specifies the name of the archive
where the form or function is stored. The archive file name must follow
the IN keyword in the REQUIRED FORMS or REQUIRED FUNCTIONS
clauses of the APPLICATION section (in the master application script).
Correction
Rewrite the REQUIRED FORMS or REQUIRED FUNCTIONS clause of

the APPLICATION section (the master application header) in the form
script script file. See

for
the syntax and usage of the APPLICATION section.
37
8526
Explanation
ACPL ERROR: A form ID was expected.
The ACCELL/SQL compiler (ACPL) expected the next token to be a form

name or function name. In the REQUIRED FORMS or REQUIRED
FUNCTIONS clause of the APPLICATION section in the master
application script, each form or function specification must begin with a
form name or function name.
Correction
Rewrite the REQUIRED FORM or REQUIRED FUNCTIONS clause of

the APPLICATION section in the master application form script script
file. See

for the syntax
and usage of the APPLICATION section.
8527
ACPL ERROR: A form, application or user function definition was
expected.
Explanation
The ACCELL/SQL compiler (ACPL) could not find a valid statement at

the beginning of a form script file.
For the master application form script file (the .as file), an
application definition must appear in the APPLICATION section.
For a standard script file (a .fs file), either a form definition must
appear in the FORM section, or an external declaration must
appear in the EXTERN and FUNCTION statements.
Correction
8528
Explanation
Correction
38
Start a standard form script file with either a form declaration (the FORM
section) or an external declaration (the EXTERN and FUNCTION
statements). Start a master application form script file with an application
declaration (the APPLICATION section). See

for the syntax and usage of form script statements
and sections.
ACPL ERROR: Display location was expected.
The ACCELL/SQL compiler (ACPL) expected the next token to be a

display location: either a screen field name or the FYI_MESSAGE
keyword. The display location must follow the FOR keyword in the
DISPLAY statement.
Find the DISPLAY statement that is missing the display location, and
rewrite the statement. Omit the FOR clause or follow the FOR keyword
with either a field name or the FYI_MESSAGE keyword. See

for the syntax and usage
of the DISPLAY statement.
8529
Explanation
Correction
8532
ACPL ERROR: The IN keyword was expected.
The IN keyword was missing from the CREATE TIMER EVENT

statement.
Add the IN keyword to the CREATE TIMER EVENT statement. IN
should be followed by an expression that specifies the minimum number
of seconds that must pass before the timer handler function is executed.
ACPL ERROR: An application, form, schema, or table ID was
expected.
Explanation

name 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 keyword
in the master application form header
A form name is required after the FORM keyword in the standard
form header.
A table name with an optional schema (or database, owner, or
user) name is required after the TARGET_TABLE keyword in the
FORM section.
A global timer function name is required after the USING TIMER
HANDLER 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 is
the name of the database object that contains the table. This database
object is a database, owner, schema or user, depending on the RDBMS on
which ACCELL/SQL is running.
Correction
Find the form script statement that is missing the application, form,
table, or database, owner, schema, or user name. Also check for the use
of variables that are not names. Rewrite the statement. See

of the form script statements.
39
8533
Explanation
Correction
8539
ACPL ERROR: A justification specification was expected.

justification specification: CENTERED, LEFT, RIGHT, or a string. A
justification specification follows the DISPLAY_JUSTIFY keyword in
the DISPLAY statement.
Find the DISPLAY statement that has the incorrect DISPLAY_JUSTIFY
clause. Omit the DISPLAY_JUSTIFY clause or follow the
DISPLAY_JUSTIFY keyword by a valid justification specification. See

of the DISPLAY statement.
ACPL ERROR: The NEXT keyword was expected.
Explanation

NEXT keyword. In a CHOOSE NEXT FORM statement, the NEXT
keyword must follow the CHOOSE keyword.
Correction
Find the CHOOSE NEXT FORM section that is missing the NEXT
keyword, and rewrite the statement. See

for the syntax and usage of the CHOOSE NEXT
FORM section.
8541
Explanation
ACPL ERROR: The RECORD keyword was expected.

RECORD keyword. The RECORD keyword is required in these
locations:
after the CURRENT keyword in the DELETE CURRENT
RECORD statement
after the CURRENT keyword in the UPDATE CURRENT
RECORD statement
after the REJECT keyword in the REJECT RECORD statement
Because the compiler can not determine if a REJECT RECORD or a
REJECT OPERATION statement was intended, error number 8620
accompanies this error message.
Correction
40
Find the form script statement that is missing the RECORD keyword,
and rewrite the statement. See

8543
Explanation
ACPL ERROR: A table name was expected.
The ACCELL/SQL compiler (ACPL) expected the next token to be a table

name. A table name is required in these locations:
after the TARGET_TABLE keyword in a FORM section of a
standard form
after an SLOCK, XLOCK or UNLOCK keyword in a lock
statement
A table name can be specified in either the table_name or
database_object.table_name format. The database_object argument is
the name of the database object that contains the table. This database
object is a database, owner, schema, or user, depending on the RDBMS
on which ACCELL/SQL is running.
Correction
8544
Find the form script statement that is missing the table name, check the
spelling of specified tables, and rewrite the statement. See

of form script statements.
ACPL ERROR: The SELECT keyword was expected.
Explanation

SELECT keyword. In this case, the SELECT keyword must appear after
the TO keyword in the SET statement.
Correction
Find the SET statement that is missing the SELECT keyword, and

for the syntax and usage of the SET and SELECT statements.
8545
ACPL ERROR: The SET keyword was expected.
Explanation

SET keyword. The SET keyword must appear after the ROW keyword in
the UPDATE SELECTED ROW statement.
Correction
Find the UPDATE SELECTED ROW statement that is missing the SET

for the syntax and usage of the UPDATE statement.
41
8546
Explanation
ACPL ERROR: An ACCELL/SQL type was expected.
The ACCELL/SQL compiler (ACPL) expected the next token to be a valid

ACCELL/SQL type keyword. This message is displayed in these cases:
An invalid return type is specified in a declaration for a global
function.
An invalid type is specified for a target variable in the LOCAL
clause in the FORM section.
Correction
If the problem is in a global function declaration, make sure that the

return type is specified by using one of the following keywords:
AMOUNT
BINARY
BOOL
DATE
DBMS_ERROR
FLOAT
NUMERIC
ROW_VALUED
STRING
TEXT
TIME
TIMER
VOID
Use the ACCELL keyword in the EXTERN statement only if the function
is an ACCELL/SQL function. Use the C keyword for C functions and the
STORED keyword for SYBASE SQL Server stored procedures.
For a target variable in the LOCAL clause, make sure that the data type is
specified by using one of the following keywords:
AMOUNT
BINARY
BOOL
8550
42
DATE
FLOAT
NUMERIC
STRING
TEXT
TIME
ACPL ERROR: The THEN keyword was expected.
Explanation

THEN keyword. In this case, the THEN keyword must follow the
expression to be evaluated in the IF statement.
Correction
Find the IF statement with the missing THEN keyword and rewrite the
statement. See

for the
syntax and usage for the IF statement.
8553
Explanation
ACPL ERROR: The TO keyword was expected.

TO 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 optional
consistency level clause, the keyword TO follows the consistency
level clause.)
after the expression to be stored in the STORE statement
after the variable or variable list in the SET statement (The
variable or variable list follows the SET keyword.)
after the ACTION, AUD_ACTION, FIND_ACTION, LABEL,
AUD_LABEL, FIND_LABEL, and KEYS keywords in the SET
COMMAND statement
Correction
8554
Find the form script statement that is missing the TO keyword, and

ACPL ERROR: The TRIM keyword was expected.
Explanation

TRIM keyword. The TRIM keyword must follow the ERASE keyword in
the ERASE TRIM statement.
Correction
Find the ERASE TRIM statement that is missing the TRIM keyword, and

for the syntax and usage of the ERASE TRIM statement.
8555
Explanation
ACPL ERROR: The TX keyword was expected.

TX keyword. The TX keyword must follow the CONTINUE, START, or
RESTART keyword in a consistency level clause of the CHOOSE NEXT
FORM or CHOOSE FIRST FORM statement.
43
This error message also occurs if no consistency level clause exists when
such a clause is expected in a CHOOSE NEXT FORM or CHOOSE
FIRST FORM section.
Correction
8556
Find the CHOOSE NEXT FORM or CHOOSE FIRST FORM statement

that is missing the TX keyword, and rewrite the statement. See

of the CHOOSE NEXT FORM or CHOOSE FIRST FORM sections.
ACPL ERROR: The UNTIL keyword was expected.
Explanation

UNTIL keyword. The UNTIL keyword must follow the statement list in
the REPEAT statement.
Correction
Find the REPEAT statement that is missing the UNTIL keyword, and

for the syntax and usage of the REPEAT statement.
8557
Explanation
ACPL ERROR: The USING keyword was expected.

USING keyword. The USING keyword must appear in these locations:
following the consistency level clause of the CHOOSE NEXT
FORM or CHOOSE FIRST FORM section or statement
following the SEC or SECONDS keyword of the CREATE TIMER
EVENT statement
Correction
44
Find the form script statement that is missing the USING keyword, and

for the syntax and usage of the CHOOSE NEXT FORM and CHOOSE
FIRST FORM sections or statements and the CREATE TIMER EVENT
statement.
8558
Explanation
ACPL ERROR: A user name was expected.

developer-defined name. A developer-defined name is required in these
cases:
for the function name after the FUNCTION keyword in a
developer-defined function that is defined in the FUNCTION
section
for the function parameters in the parameter list of a
developer-defined function defined in the FUNCTION section
Correction
8560
Explanation
Correction
8563
Explanation
Find the FUNCTION section that is missing the developer-defined name,


for the syntax and usage of the FUNCTION section.
ACPL ERROR: A variable was expected.

variable name. This error can occur wherever the grammar calls for a
variable specification and one is not found.
Find the form script statement that has the missing or incorrect variable
name. See

for the syntax
and usage of form script statements.
ACPL ERROR: The ZOOM keyword was expected.

ZOOM 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.
Correction
8564
Explanation
Find the ENABLE ZOOM or DISABLE ZOOM statement that is missing

the ZOOM keyword, and rewrite the statement. See

for the syntax and usage of these form
script statements.
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 compiler
function found the failed memory allocation.
45
This error is not caused by a syntax error in your form script script.
Correction
Try one of the following solutions:

If the system did not have enough system memory or swap space
available when you executed the compiler, try executing the
compiler again. This situation can occur on heavily loaded
systems.
If the compiler ran out of memory on a large form script script
(over 1000 lines), try reducing the complexity of the form script
script. Create global form script functions to perform tasks that are
repeated.
If you still encounter memory allocation problems, call Unify Customer
Support.
8565
Explanation
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. This
error occurs in the following cases:
ACPL was called with the y option and was unable to open the
symbol table output file.
ACPL was called with the c option and was unable to open the
code output file.

ACPL could not open the script file to be compiled. This case can
occur if you omit the a option (and the i option is not used)
when trying to compile a master application script file.
Correction
Take these actions:

Make sure that you have write and execute permission on the
current directory.
Make sure you have read and write permission on the file being
opened.
Make sure that the operating system has enough resources (open
file descriptors and inodes) to open a new file.
46
8566
Explanation
Correction
8567
ACPL ERROR: An illegal character was ignored.
The script file contained an ASCII character that the ACCELL/SQL

compiler (ACPL) could not interpret.
Search the script file for invalid or non-printable ASCII characters and
remove them.
ACPL ERROR: An ACCELL/SQL statement was expected.
Explanation

start of a new form script statement. This error can occur in control flow
statements (FOR, IF, REPEAT, WHILE, and SWITCH), when the
statement being controlled by the control flow statement is not specified.
Correction
Find the form script control statement with the missing statement and be
sure to specify the statement under control of the control flow statement.
See

for the syntax and
usage of the form script control statements.
8568
ACPL ERROR: An attribute was expected.
Explanation

attribute. When a variable name is followed by a colon (:), the name of
an attribute must follow the colon.
Correction
Find the form script statement that contains the incorrect variable name,
and either remove the colon or add a valid attribute name. For the
descriptions of the ACCELL/SQL attributes, see

.
8569
Explanation
ACPL ERROR: A form code section name was expected.
The ACCELL/SQL compiler (ACPL) expected the next token to identify

an AFTER event or BEFORE event section such as BEFORE FORM,
AFTER ZOOM, and so on. The second keyword must follow the AFTER
keyword or BEFORE keyword in one of the following event sections:
47
AFTER ADD
AFTER APPLICATION
AFTER DELETE
AFTER FIELD
AFTER FIND
AFTER FORM RETURN
AFTER UPDATE
AFTER ZOOM
Correction
8573
BEFORE
BEFORE
BEFORE
BEFORE
BEFORE
BEFORE
BEFORE
BEFORE
ADD
APPLICATION
DELETE
FIELD
FIND
FORM
RECORD
UPDATE
Find the AFTER or BEFORE section that is missing the second keyword,
and rewrite the section. See

ACPL ERROR: Either the KEY or VALUES keyword was
expected.
Explanation

KEY keyword. Either the KEY or the VALUES keyword must follow the
RETURN keyword in the RETURN KEY clause of the ENABLE ZOOM
statement.
Correction
8575
ACPL ERROR: The CASE or DEFAULT keyword was expected.
Explanation
The ACCELL/SQL compiler (ACPL) expected the next token to be either

the CASE or DEFAULT keyword. Either the CASE or DEFAULT
keyword must follow the BEGIN keyword in the SWITCH statement.
Correction
Find the SWITCH statement that is missing the CASE and DEFAULT
keywords, and rewrite the statement to use one of them. See

of the SWITCH statement.
8577
Explanation
48
Find the ENABLE ZOOM statement that is missing the KEY or VALUES

for the syntax and usage of the ENABLE ZOOM
statement.
ACPL ERROR: The CHANGES keyword was expected.

CHANGES keyword. The CHANGES keyword must follow the FIELD
keyword in the WHEN FIELD CHANGES section.
Correction
8578
Explanation
Correction
8580
Explanation
Find the WHEN FIELD CHANGES section that is missing the

CHANGES keyword, and rewrite the subsection. See

for the syntax and usage of the WHEN
FIELD CHANGES section.
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.
ACPL ERROR: There was a bad conversion.
The ACCELL/SQL compiler (ACPL) was unable to convert a character

string representation of a constant to a constant type. This error occurs in
two cases:
ACPL ran out of memory.
ACPL found an internal conversion routine error.
Correction
If you suspect that ACPL has run out of memory, try reducing the
complexity of the form script script. You can also create global form
script 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.
Explanation
As the ACCELL/SQL compiler (ACPL) processes a script file, it builds

three internal tables to keep track of symbols. These tables are called
local, external, and ambiguous, each tracking a different symbol type.
This error occurs if one of the tables runs out of space.
Correction
Reduce the complexity of the script by decreasing the number of

variables in the symbol_type table. You can try creating global form
script functions to handle tasks which occur in several places. See

for more information about writing
global form script functions.
49
8582
Explanation
The ACCELL/SQL compiler (ACPL) ran out of internal registers as it

attempted 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 processes
an expression.
Correction
Find the expression that is causing the error and reduce the complexity of
this expression. Use ACCELL/SQL variables to hold intermediate values
in the expression.
8583
Explanation
Correction
8584
ACPL ERROR: An attribute needs a variable name specified.
The ACCELL/SQL compiler (ACPL) found an attribute that has no

corresponding variable. An attribute must be preceded by a variable
name followed by a colon (:). The name of an attribute must follow the
colon.
Find the form script statement that has the incorrect attribute name and
either remove the attribute or add a valid variable name. See

information about form
script attributes.
ACPL ERROR: Too many errors, cant continue.
Explanation
The ACCELL/SQL compiler (ACPL) found the maximum number of

errors (10) in the script file. The compiler does not stop processing a
script file when it finds the first error. Instead, ACPL attempts to check
the whole file for errors. Once it found 10 errors, the compiler displays
this error message and stops processing the script file.
Correction
Fix the syntax errors that have caused the existing error messages, and
then recompile the script file.
8585
50
ACPL ERROR: No free registers, the expression is too complex.
ACPL ERROR: There is a bad system variable.
Explanation

system variable but found instead an invalid variable name.
Correction
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.
8587
Explanation
Correction
ACPL ERROR: Table name not found in data dictionary.
The ACCELL/SQL compiler (ACPL) could not find information for a

database table in the database. The compiler searches the database for
table information when compiling the TARGET_TABLE clause of the
FORM section.
Find the form script statement that is causing the error and verify that the
table is defined in the current database, owner, schema, or user. Whether
the table is contained in a database, owner, schema, or user depends on
the RDBMS on which ACCELl/SQL is running.
Correct the table name and substitute a valid table name. Also make sure
that the database has not been corrupted. See

for the syntax and usage of the form script
statements.
8588
Explanation
ACPL ERROR: No columns can be found.
The ACCELL/SQL compiler (ACPL) cannot find column information in

the database. The compiler searches the database for column information
in the following instances:
When processing a standard form, ACPL searches the database for
information about the columns in the table specified by the the
TARGET_TABLE clause of the FORM section.
Before writing the compiled form script to a file, ACPL searches
the database for information about each local symbol that is a
target field.
Correction
8590
Explanation
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 been
corrupted.
ACPL ERROR: An expression was expected.

expression in a search ranges expression list. A search range expression
list contains search range values for a CLEAR_FIND_EXP target
attribute.
51
Correction
Find the SET statement that sets the CLEAR_FIND_EXP target attribute,
and rewrite the search ranges expression list so that each element in this
list begins with either an expression or the Clear-to-find expression
operator (=>).
See

for the syntax and
usage of the SET statement and

for
information about the Clear-to-Find expression operator.
8591
Explanation
Correction
8592
Explanation
ACPL ERROR: The ACTION keyword was expected.

ACTION keyword. The compiler was looking for the ACTION keyword
after the NEXT keyword in the NEXT ACTION statement.
Find the NEXT ACTION statement that is missing the ACTION

for the syntax and usage of the NEXT ACTION
statement.
ACPL ERROR: The RECORD or FORM keyword was expected.

the RECORD or FORM keyword. Either RECORD or FORM is required
in these cases:
after the NEXT keyword in either an ON NEXT FORM or an ON
NEXT RECORD event section
after the PREVIOUS keyword in either an ON PREVIOUS FORM
or an ON PREVIOUS RECORD event section
Correction
8593
Explanation
Find the event section that is missing the RECORD or FORM keyword,
and rewrite the section. See

ACPL ERROR: The ADD or FIND keyword was expected.

the ADD or FIND keyword.
Either ADD or FIND is required in the NEXT ACTION IS CLEAR TO
ADD or the NEXT ACTION IS CLEAR TO FIND statement. Because the
TO 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).
52
Correction
Find the NEXT ACTION statement that is missing the ADD or FIND
keyword in the CLEAR TO clause, and rewrite the statement. See

of the NEXT ACTION statement.
8595
ACPL ERROR: The variable list doesnt match # of scalar_db_exps.
Explanation
The ACCELL/SQL compiler (ACPL) found a SET statement that contains

a variable list and a stored procedure call, but the stored procedure is not
ROW_VALUED. Before a stored procedure can be used in a SET
statement that contains a variable list, the stored procedure must be
declared as ROW_VALUED in the EXTERN statement.
Correction
Find the SET statement and EXTERN statements that reference the stored
procedures and rewrite the appropriate statements. See

for the syntax and usage of the SET and
EXTERN statements.
8598
Explanation
Correction
8599
Explanation
ACPL ERROR: The FIRST keyword was expected.

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

of the CHOOSE FIRST FORM statement.
ACPL ERROR: Language section not valid in a Standard Form.
The ACCELL/SQL compiler (ACPL) found either the BEFORE

APPLICATION or the AFTER APPLICATION section in a standard form
script. These sections can appear only in a master application form script.
Correction
Find the BEFORE APPLICATION or AFTER APPLICATION section in

the standard form script, and remove it. Either move the section to the
master application form script, or find another valid section in a standard
form script in which to execute the associated form script statements. See

of the BEFORE APPLICATION and AFTER APPLICATION sections.
53
8600
Explanation
ACPL ERROR: The CONSTANT expression was expected.

constant. 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 DEFINE
COMMAND section
the label, action, and key strings in the DEFINE COMMAND
section
Correction
8601
Find the SWITCH statement that is missing the constant in a CASE

clause, and rewrite the statement. See

for the syntax and usage of the SWITCH statement.
ACPL ERROR: More than one default expression in switch
statement.
Explanation
Correction
8602
54
The ACCELL/SQL compiler (ACPL) found more than one DEFAULT

clause in a SWITCH statement.
Find the SWITCH statement that has the multiple DEFAULT clauses, and
remove all but one of the DEFAULT clauses. See

for the syntax and usage of the SWITCH
statement.
ACPL ERROR: There is an UNDEFINED function.
Explanation
The ACCELL/SQL compiler (ACPL) found an undefined function. The

compiler builds a table that contains information about all
developer-defined functions. This error occurs if the compiler cannot find
an entry in this tables for a function called from a form script statement.
Correction
Find the form script statement that contains the undefined function name.
Make sure the C-hook function is defined and declared, that it is spelled
the same way it has been defined, and that it is linked into the
application. See

for more
information about writing C-hook functions.
8603
Explanation
Correction
8604
ACPL ERROR: The number of parameters do not match.
The ACCELL/SQL compiler (ACPL) found a function or stored procedure

call 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 are
using the correct function or stored procedure name and the correct
number of arguments in the function or stored procedure call.
ACPL ERROR: A result parameter was expected.
Explanation
The ACCELL/SQL compiler (ACPL) found a function or stored procedure

call that contains a constant argument when the compiler expected a
variable. The compiler builds a table that contains information about all
developer-defined functions and stored procedures for the script. This
information also indicates whether each parameter was declared as a
RESULT parameter. A RESULT parameter requires a variable as an
argument.
Correction
Find the form script statement that contains the function or stored
procedure call that contains the incorrect argument. Make sure that you
are using the correct function or stored procedure name and the
appropriate argument for each parameter. Use a variable for a RESULT or
REFERENCE parameter and a constant or variable for a non-RESULT
parameter.
8605
ACPL ERROR: A function was redeclared.
Explanation
The ACCELL/SQL compiler (ACPL) found a declaration for a function or

stored procedure that has already been declared in the script. The
function or stored procedure can be declared only once in the script.
Correction
Find the duplicate declaration, usually an EXTERN statement, and delete

it. See

for the syntax and
usage of the EXTERN statement.
55
8607
ACPL ERROR: TO keyword expected after the keywords ON

CLEAR.
Explanation

TO keyword, after the CLEAR keyword in the ON CLEAR TO ADD or
ON CLEAR TO FIND section.
Correction
Find the ON CLEAR TO ADD or ON CLEAR TO FIND section that is

missing the TO keyword, and rewrite the section. See

for the syntax and usage of the ON
CLEAR TO ADD and ON CLEAR TO FIND sections.
8611
ACPL ERROR: There was an error in a control structure break call.
Explanation
The ACCELL/SQL compiler found a CONTINUE statement for breaking

out of the current iteration of a control structure, but the CONTINUE
statement was not in one of the loop statements (FOR, REPEAT, SET . . .
SELECT EXECUTING, or WHILE).
Correction
Remove the CONTINUE statement causing the error or rewrite the script
so that the CONTINUE statement is in a loop statement.
8613
ACPL ERROR: SET_CONSISTENCY or RECORD_CONSISTENCY
keyword expected.
56
Explanation

the SET_CONSISTENCY or RECORD_CONSISTENCY keyword, after
the keyword TX in the CONTINUE TX or START TX consistency level
clauses of a CHOOSE . . . FORM statement.
Correction
Find the CHOOSE FIRST FORM or CHOOSE NEXT FORM statement

that is missing the SET_CONSISTENCY or RECORD_CONSISTENCY
keyword in the consistency level clause. If the transaction level is either
CONTINUE TX or START TX, the consistency keyword must be either
SET_CONSISTENCY or RECORD_CONSISTENCY. See

for the syntax and usage of the CHOOSE
FIRST FORM and CHOOSE NEXT FORM statements.
8614
ACPL ERROR: A FIND, NEXT or PREVIOUS keyword was
expected.
Explanation
The ACCELL/SQL compiler (ACPL) expected the next token to be one of

the keywords that can follow the ON keyword. One of the following
keywords must follow the ON keyword in an event section:
CLEAR (ON CLEAR TO ADD or ON CLEAR TO FIND)
EXIT (ON EXIT)
FIND (ON FIND)
NEXT (ON NEXT FORM or ON NEXT RECORD)
PREVIOUS (ON PREVIOUS FORM or ON PREVIOUS RECORD
Correction
8615
Explanation
Find the event section that contains the incorrect keyword after the ON
keyword, and rewrite the section. See

ACPL ERROR: A PIPELINE was expected.

PIPELINE keyword. The PIPELINE keyword is required after these
keywords:
CREATE in a CREATE PIPELINE statement
WRITE in a WRITE PIPELINE statement
CLOSE in a CLOSE PIPELINE statement
Correction
8616
Find the form script pipeline statement that is missing the PIPELINE

for the syntax and usage of the form script pipeline
statements.
ACPL ERROR: Statement can only occur in an ON FIELD code
section.
Explanation
The ACCELL/SQL compiler (ACPL) found either an INPUT or a

RESTART ON FIELD statement in an event section that is not the ON
FIELD section. The INPUT or a RESTART ON FIELD statements are
valid only in the ON FIELD section.
Correction
Find the INPUT or RESTART ON FIELD statement and move it to an

ON FIELD section. See

for the syntax and usage of the ON FIELD subsection.
57
8617
Explanation
ACPL ERROR: There is a bad function type.
The ACCELL/SQL compiler (ACPL) expected the next token to be the C,

ACCELL, or STORED keyword. One of these function type keywords
must follow the EXTERN keyword in a developer-defined function
declaration.
Correction
8618
Find the EXTERN statement at the beginning of the script file and make
sure the function type is C for C-hook functions, ACCELL for form
script functions, or STORED for stored procedures. See

for the syntax and usage of the EXTERN
statement.
ACPL ERROR: A target attribute is not allowed.
Explanation
The ACCELL/SQL compiler (ACPL) found a target variable attribute in a

variable name, but this variable is not a target or target field variable.
Correction
Find the form script statement that contains the incorrect target attribute.
Either correct the variable name or change the attribute name. See

for information about
variable attributes.
8619
ACPL ERROR: Statement can only occur in an ON FIND code
section.
Explanation
The ACCELL/SQL compiler (ACPL) found a REJECT RECORD

statement in an event section that is not the ON FIND section. The
REJECT RECORD statement is valid only in the ON FIND section.
Correction
Find the REJECT RECORD statement, and move it to an ON FIND

section. See

for the
syntax and usage of the ON FIND section.
8620
Explanation
58
ACPL ERROR: The OPERATION keyword was expected.

the RECORD or OPERATION keyword. One of these keywords must
follow the REJECT keyword in either the REJECT RECORD or
REJECT OPERATION statement.
Because the compiler can not determine whether a REJECT RECORD or

a REJECT OPERATION statement was intended, error number 8541
also accompanies this error message.
Correction
Find the REJECT RECORD or REJECT OPERATION statement that is

missing the RECORD or OPERATION keyword, and rewrite the
statement. See

for the
syntax and usage of the REJECT RECORD and REJECT OPERATION
statements.
8624
ACPL ERROR: Statement may not occur in an ON FIND code section.
Explanation
The ACCELL/SQL compiler (ACPL) found a NEXT ACTION statement

in the ON FIND event section. NEXT ACTION is invalid in the ON FIND
section.
Correction
Find the NEXT ACTION statement, and move it to another event section.
See

for the syntax and
usage of the ON FIND section and the NEXT ACTION statement.
8625
ACPL ERROR: Statement may not occur in an INIT FIELD code
section.
Explanation

in the INIT FIELD event section. All uses of NEXT ACTION are invalid
in the INIT FIELD section except for NEXT ACTION IS PREVIOUS
FORM .
Correction
Find the NEXT ACTION statement and move it to another event section.
See

for the syntax and
usage of the INIT FIELD subsection and the NEXT ACTION statement.
8626
Explanation
Correction
ACPL ERROR: Statement may not occur in an AFTER

APPLICATION code section.

in the AFTER APPLICATION event section. NEXT ACTION is invalid
in the AFTER APPLICATION section.
See

for the syntax and
usage of the AFTER APPLICATION section and the NEXT ACTION
statement.
59
8627
ACPL ERROR: Statement may not occur in a BEFORE

APPLICATION code section.
Explanation

in the BEFORE APPLICATION event section. NEXT ACTION is invalid
in the BEFORE APPLICATION section.
Correction
See

for the syntax and
usage of the BEFORE APPLICATION section and the NEXT ACTION
statement.
8628
ACPL ERROR: Statement may not occur in a WHEN FIELD

CHANGES code section.
Explanation

in the WHEN FIELD CHANGES form script section. NEXT ACTION is
invalid in the WHEN FIELD CHANGES section.
Correction
See

for the syntax and
usage of the WHEN FIELD CHANGES subsection and the NEXT
ACTION statement.
8629
ACPL ERROR: Statement may not occur in a BEFORE FORM code
section.
Explanation
Correction
60

in the BEFORE FORM event section. NEXT ACTION is invalid in the
BEFORE FORM section.
See

for the syntax and
usage of the BEFORE FORM section and the NEXT ACTION statement.
8630
ACPL ERROR: There is a bad master application variable.
Explanation
The ACCELL/SQL compiler (ACPL) expected a variable name to follow

the string application_name:, where application_name is the name of
the application and the name of the master application form.
Correction
Find the incorrect master application form variable name and follow
application_name: with the name of a master application form
variable. See

for more information
on variable names.
8631
ACPL ERROR: There are Too many program names (pipes) in the
program list.
Explanation
Correction
8632
Explanation
Correction
8633
Explanation
The ACCELL/SQL compiler (ACPL) found more than eight program

names in the program list of a CREATE PIPELINE statement. Up to
eight program names are allowed in a program list.
Find the CREATE PIPELINE statement, and rewrite the program list so
that no more than eight program names are listed. See

for the syntax and usage of the CREATE
PIPELINE statement.
ACPL ERROR: The statement may not occur in current code section.
The ACCELL/SQL compiler (ACPL) found an invalid form script

statement in an event section.
Find the invalid statement, and remove it from the current event section.
See

on which statements have restrictions for the event sections in which
they are valid.
ACPL ERROR: The SCREEN keyword was expected.

SCREEN keyword. The SCREEN keyword must follow these keywords:
REFRESH in a REFRESH SCREEN statement
REPAINT in a REPAINT SCREEN statement
61
Correction
8634
ACPL ERROR: Must use START TX in an application.
Explanation

START keyword in a consistency level clause of the CHOOSE FIRST
FORM statement. In the CHOOSE FIRST FORM statement, the
transaction level in the consistency level clause must be START TX. The
CONTINUE TX and RESTART TX transaction levels are allowed only in
the CHOOSE NEXT FORM statement in a standard form.
Correction
Find the CHOOSE FIRST FORM statement that contains the incorrect
transaction level, and rewrite the consistency level clause to use START
TX. See

for the syntax
and usage of the CHOOSE FIRST FORM statement.
8635
Explanation
Correction
8637
Explanation
Correction
62
Find the REFRESH SCREEN or REPAINT SCREEN statement that is

missing the SCREEN keyword, and rewrite the statement. See

of the REFRESH SCREEN and REPAINT SCREEN statements.
ACPL ERROR: There was a duplication of a code section.
The ACCELL/SQL compiler (ACPL) found an event section that has

already been processed. Each event section can occur only once in a form
script file.
Find the duplicate event section, and determine which section to delete.
ACPL ERROR: The BY keyword was expected.

BY keyword, which must follow the IDENTIFIED keyword in the
INSTALL statement.
Find the INSTALL statement that is missing the BY keyword and rewrite
the statement. See

for the
syntax and usage of the SET/SELECT statement.
8639
ACPL ERROR: String constants exceeded the maximum number for
a form.
Explanation
The ACCELL/SQL compiler (ACPL) found more than 8192 (6144 on

DOS systems) string constants in the script file. A string constant is a
series of characters enclosed in single quotes, for example, dog.
Correction
Try splitting the form or making it less complicated. You can use the
ACCELL/SQL message file system functions (open_message_file$( ),
close_message_file$( ), and get_message$( )) to access strings from a

message file. See

for
more information about the system functions for accessing a message
file.
8640
Explanation
Correction
8641
Explanation
ACPL ERROR: Exceeded maximum allowed nesting level.
The ACCELL/SQL compiler (ACPL) found control statements nested

more than eight levels deep. As the compiler processes control
statements in which nesting can occur (FOR, IF, REPEAT, SWITCH,
WHILE), it keeps track of the nesting level.
Find the form script control statements that are nested for more than
eight levels and rewrite the statements to reduce the number of nesting
levels. See

for the syntax
and usage of the form script control statements.
ACPL ERROR: The RETURN keyword was expected.

RETURN keyword. The RETURN keyword must follow these keywords:
the FORM keyword in the AFTER FORM RETURN section
the ZOOM keyword in the ZOOM RETURN VALUES statement
Correction
Find the AFTER FORM RETURN section that is missing the RETURN
keyword, and rewrite the section. See

for the syntax and usage of the AFTER FORM
RETURN section.
63
8643
Explanation
Correction
8644
Explanation
Correction
8645

FUNCTIONS keyword, following the REQUIRED keyword in the
REQUIRED FUNCTIONS clause of the master application header.
Find the REQUIRED FUNCTIONS clause of the APPLICATION section
that is missing the FUNCTIONS keyword, and rewrite the section. See

of the APPLICATION section.
ACPL ERROR: The ON keyword was expected.

ON keyword, following the RESTART keyword in the RESTART ON
FIELD statement.
Find the RESTART ON FIELD statement with the missing ON keyword

for the syntax and usage of the RESTART ON FIELD section.
ACPL ERROR: Invalid function key number.
Explanation
The ACCELL/SQL compiler (ACPL) found an invalid function number.

Valid function numbers are in the range 0 through 99. Function numbers
can be specified in the SET COMMAND statement and the DEFINE
COMMAND section.
Correction
Find the SET COMMAND statement or the DEFINE COMMAND section

that contains the invalid function key number, and correct the function
key number. See

for the
syntax and usage of this statement and section.
8646
Explanation
Correction
64
ACPL ERROR: The FUNCTIONS keyword was expected.
ACPL ERROR: The FOR keyword was expected.
The FOR keyword was missing from the INSTALL DBMS_ERROR

HANDLER statement.
Add the FOR EVENTS clause to the INSTALL DBMS_ERROR
HANDLER statement.
8648
Explanation
Correction
8649
Explanation
Correction
8651
ACPL ERROR: Invalid mode specified.
The ACCELL/SQL compiler (ACPL) found an invalid command action

attribute or an invalid prompt attribute while parsing the DEFINE
COMMAND section or the SET COMMAND statement.
Find the DEFINE COMMAND section or the SET COMMAND statement
that contains the invalid command attribute and rewrite the statement.
See

for the syntax and
usage of the DEFINE COMMAND section and the SET COMMAND
statement.
ACPL ERROR: The IS keyword was expected.
Encountered the NOT keyword without the IS keyword. Usually used

like IS NOT UNDEFINED.
Add the IS keyword before the NOT keyword.
ACPL ERROR: Display variables may not have code sections.
Explanation
The ACCELL/SQL compiler (ACPL) found a system information field

while parsing a FIELD section. System information fields (like
zoom_indicator and record_state) are not permitted as field names in a
FIELD section.
Correction
Find the FIELD section that has the system information field name, and
rewrite the section to use a developer-defined field name. See

of the FIELD section.
8652
Explanation
Correction
ACPL ERROR: Could not open database.
The ACCELL/SQL compiler (ACPL) cannot open the database.

To correct the problem, take these steps:
1. Make sure that the correct application directory is current.
2. Make sure that you have correctly set the variables used by your
RDBMS to find the database (shown in the following table)
65
If you are using:
Then set:
INFORMIX Online
INFORMIXDIR and TBCONFIG
INFORMIX SE
DBPATH and INFORMIXDIR
INGRES
DBNAME and II_SYSTEM
ORACLE
ORACLE_HOME and ORACLE_SID
SYBASE SQL Server
SYBASE and DSQUERY
Unify DataServer
DBPATH and DBNAME
See ACCELL/SQL: Configuration Variable and Utility References

for information about these configuration variables.
3. Make sure that the UNIFY configuration variable is set correctly.
4. Verify that you have permission to access the database.
5. Check the read and write permissions on the database files.
For Unify DataServer only:
If the database has been shutdown, you may not be able to open
the database.
Make sure that the AUTOSTART and OWNERSTART configuration
variables do not prevent you from opening the database. These
variables control who may start (initially open) the database. For
information about these Unify DataServer configuration variables,
see UNIFY 2000: Configuration Variable and Utility Reference.
8657
ACPL ERROR: Cannot change to the specified schema or database.
Explanation
ACCELL/SQL was unable to access the specified schema or database for
one of the following reasons:

The current user does not have the required permissions.
The schema or database does not exist.
The correct database or server has not been specified.
66
Correction
To solve the problem, take these steps:

1. Verify that you have permission to access the specified schema or
database.
2. Verify that the DBUSER and DBNAME configuration variables are
set correctly
3. Verify that any schema or database specified on the command line,
using the S option, is valid.
4. If you are using the SYBASE SQL Server RDBMS, verify that the
DSQUERY configuration variable is set correctly.
5. If you are using the Unify DataServer RDBMS, verify that the
DBPATH configuration variable is set correctly.
See
s for
information about these configuration variables.
8658
Explanation
Correction
8659
Explanation
ACPL ERROR: Invalid action specified for NEXT ACTION statement.
The ACCELL/SQL compiler (ACPL) detected an invalid action specifier

while parsing the NEXT ACTION statement. This error occurs if an
invalid action has been specified in the current section.
Find the NEXT ACTION statement that contains the invalid action
specifier. and rewrite the statement. See

for the syntax and usage of the NEXT ACTION
statement.
ACPL ERROR: The token WORK was expected.

WORK keyword. The WORK keyword must follow these keywords:
the ROLLBACK keyword in the ROLLBACK WORK statement
the COMMIT keyword in the COMMIT WORK statement
Correction
Find the ROLLBACK WORK or COMMIT WORK statement that is

missing the WORK keyword and rewrite the statement. See

of the ROLLBACK WORK and COMMIT WORK statements.
67
8661
Explanation
The ACCELL/SQL compiler (ACPL) expected to find the tokens IS

UNDEFINED instead of the tokens = UNDEFINED.
Correction
Replace the string = UNDEFINED with the string IS UNDEFINED.
8662
ACPL ERROR: The keyword NULL is not permitted in this context.
Explanation
Correction
8663
Explanation
Correction
8665
68
ACPL ERROR: IS UNDEFINED was expected.
The ACCELL/SQL compiler (ACPL) found the NULL constant as an

operand in an arithmetic, relational, logical, or bitwise operation.
Find the expression that contains the NULL keyword, and remove the
NULL keyword. For more information about using NULL in operations,
see
.
ACPL ERROR: NULL or UNDEFINED unexpected.
The ACCELL/SQL compiler (ACPL) expected either the NULL or

UNDEFINED keyword to be used as the rightmost operand of an IS or an
IS NOT operator.
Find the IS or IS NOT operator that is missing the NULL or
UNDEFINED keyword, and replace the rightmost operand with either
NULL or UNDEFINED. For more information on the IS and IS NOT
operators, see
.
ACPL ERROR: Error creating object_file, error number os_error.
Explanation
The ACCELL/SQL compiler (ACPL) cannot create the object file named
object_file (the .fo or .ao file). The error number, os_error, is the error
number returned by the operating system to indicate why the object file
cannot be created.
Correction
Make sure you have read and write permissions in the current directory.
Verify that there is enough space to create the new object file. See your
operating system manuals for information about the error number
returned by the operating system.
8666
Explanation
Correction
8667
ACPL ERROR: Error reading object_file, error number os_error.
After creating the object file, the ACCELL/SQL compiler (ACPL)

attempts to read the object file header to verify that the file was created
correctly. This error occurs if the compiler cannot read this header. The
error number, os_error, is the error number returned by the operating
system to indicate why the object file cannot be read.
See your operating system manuals for information about the error
number returned by the operating system.
ACPL ERROR: Error adding object_file, error number os_error.
Explanation
An error occurred while the ACCELL/SQL compiler (ACPL) was writing

to the object file named object_file. The error number, os_error, is the
error number returned by the operating system to indicate why the object
file cannot be read.
Correction
Make sure you have read and write permissions in the current directory.
Verify that there is enough space to save the object file. See your
8668
Explanation
Correction
8669
Explanation
Correction
ACPL ERROR: Error closing object_file, error number os_error.
An error occurred while the ACCELL/SQL compiler (ACPL) was trying

to close the object file named object_file. The error number, os_error, is
the error number returned by the operating system to indicate why the
object file could not be closed.
Verify that there is enough space to save the object file. See your
ACPL ERROR: Fatal preprocessor error in 4GL script script_file.
Before compiling the script file, the ACCELL/SQL compiler (ACPL) runs
the C preprocessor on the script. This error occurs if the C preprocessor
finds many errors in the script file named script_file.
This error should be preceded by other error messages from the C
preprocessor. See your operating system documentation on the C
preprocessor for assistance.
69
8671
Explanation
A DISPLAY TRIM statement included the FROM clause, but the FROM
clause is invalid in the DISPLAY TRIM statement.
Correction
Locate the problem DISPLAY TRIM statement, and remove the FROM
clause, or change the statement to a DISPLAY HELP statement.
8672
Explanation
Correction
ACPL ERROR: Could not get database information.

ACCELL/SQL cannot access its own information about the current
RDBMS. This error should not normally occur.
Make sure that the DBTYPE environment variable is set correctly. If

DBTYPE is set correctly, please contact Unify Customer Support.
8673
ACPL ERROR: Type cannot be specified in a functions local clause.
Explanation
The data types of target variables can be specified in the LOCAL clause
of the form declaration in a form script script. This error indicates that a
data type was found in the LOCAL clause of a local or global function,
which is invalid.
Correction
8674
Explanation
Correction
8675
Explanation
Correction
70
Use of FROM clause is valid only with DISPLAY HELP.
Find the problem LOCAL clause, and correct the error.
ACPL ERROR: Type cannot be specified for an attribute.
data type was found after an attribute rather than a variable.
ACPL ERROR: Type cannot be specified for an external variable.
data type was found after an external variable, which is invalid.
8676
Explanation
Correction
ACPL ERROR: Type can only be specified for a target variable.
data type was found after a non-target variable, which is invalid.
8677
ACPL ERROR: Type specified does not match target columns type.
Explanation
of the form declaration in a form script script. This error indicates that
the data type specified for a target variable is incompatible with the
corresponding database columns data type.
Correction
8678
Explanation
Correction
8679
ACPL ERROR: The VALUES keyword was expected.
The ACCELL/SQL compiler expected to find the VALUES keyword

following the ZOOM RETURN keywords in a ZOOM RETURN
VALUES statement.
Find the ZOOM RETURN VALUES statement that is missing the
VALUES keyword, and rewrite the statement.
ACPL ERROR: Object name is ambiguous found in more than one
schema.
Explanation
Correction
The compiler found a table name that is ambiguous in the database.

Find the problem statement, and qualify the table name with the name of
the database object that contains the table. This database object is a
database, owner, schema, or user, depending on the RDBMS on which
ACCELL/SQL is running.
71
8681
ACPL ERROR: Call of a row-valued stored procedure in an
expression.
Explanation
Row-valued stored procedures can be used in ACCELL/SQL expressions.

Stored procedures of this type return multiple rows and, can therefore be
used only as part of a SET statement.
Correction
If the stored procedure is incorrectly defined, redefine it to be a

NUMERIC stored procedure. Otherwise, modify the affected form script
statements to first store the results of the stored procedure in a general
variable; then use this general variable in the expressions.
8682
ACPL ERROR: Programmable function keys are no longer
supported.
Explanation
Correction
8683
Explanation
Correction
72
The ACCELL/SQL compiler (ACPL) found either an ON

FUNCTION_KEY section or SET FUNCTION_KEY statement. These
statements have been replaced by the DEFINE COMMAND section and
SET COMMAND statement.
Find the ON FUNCTION_KEY section or SET FUNCTION_KEY
statement and rewrite it by using the DEFINE COMMAND section or
SET COMMAND statement. For more information about using the
DEFINE COMMAND section or SET COMMAND statement, see

.
ACPL ERROR: Duplicate command key(s) attribute clause.
The ACCELL/SQL compiler (ACPL) found more than one instance of the
KEY[S] command attribute clause in a DEFINE COMMAND section.
Only one occurrence of a KEY[S] command attribute clause is allowed in
a DEFINE COMMAND section.
Find the DEFINE COMMAND section that has the multiple KEY[S]
command attribute clauses and remove all but one of the clauses. For
more information about the command attribute clauses allowed in the
DEFINE COMMAND section, see

.
8684
Explanation
ACPL ERROR: Duplicate ACTION command action attribute clause.
The ACCELL/SQL compiler (ACPL) found more than one instance of an

ACTION command attribute in a DEFINE COMMAND section. Only one
occurrence of an ACTION command attribute is permitted in a DEFINE
COMMAND section.
Correction
Find the DEFINE COMMAND section that has the multiple ACTION
command attributes and remove all but one of the attributes. For more
information about the ACTION command attributes allowed in the

.
8685
ACPL ERROR: Duplicate AUD_ACTION command action attribute
clause.
Explanation

AUD_ACTION command attribute in a DEFINE COMMAND section.
Only one occurrence of an AUD_ACTION command attribute is
permitted in a DEFINE COMMAND section.
Correction
Find the DEFINE COMMAND section that has the multiple

AUD_ACTION command attributes and remove all but one of the
AUD_ACTION command attributes. For more information about the
command action attributes allowed in the DEFINE COMMAND section,
see

.
8686
ACPL ERROR: Duplicate FIND_ACTION command action attribute
clause.
Explanation
The ACCELL/SQL compiler (ACPL) found more than one instance of a

FIND_ACTION command attribute in a DEFINE COMMAND section.
Only one occurrence of a FIND_ACTION command attribute is permitted
in a DEFINE COMMAND section.
Correction
Find the DEFINE COMMAND section with the multiple FIND_ACTION

command attributes and remove all but one of the FIND_ACTION
command attributes. For more information about the command action
attributes allowed in the DEFINE COMMAND section, see

.
73
8687
ACPL ERROR: Duplicate LABEL command label action attribute
clause.
Explanation
Correction
8688

LABEL command attribute in a DEFINE COMMAND section. Only one
occurrence of a LABEL command attribute is permitted in a DEFINE
COMMAND section.
Find the DEFINE COMMAND section that has the multiple LABEL
command attributes and remove all but one of the attributes. For more
information about the LABEL command attributes allowed in the

.
ACPL ERROR: Duplicate AUD_LABEL command label action
attribute clause.
Explanation
Correction
8689
Explanation
Correction
74

AUD_LABEL command attribute in a DEFINE COMMAND section.
Only one occurrence of an AUD_LABEL command attribute is permitted
in a DEFINE COMMAND section.
AUD_LABEL command attributes and remove all but one of these
attributes. For more information about the LABEL command attributes
allowed in the DEFINE COMMAND section, see

.
ACPL ERROR: Duplicate FIND_LABEL command label action

attribute clause.

FIND_LABEL command attribute clauses in a DEFINE COMMAND
section. Only one occurrence of a FIND_LABEL command attribute is
permitted in a DEFINE COMMAND section.
FIND_LABEL command attributes and remove all but one of these
attributes. For more information about the FIND_LABEL command
attributes allowed in the DEFINE COMMAND section, see

.
8692
Explanation
ACPL ERROR: No command name was specified.
The ACCELL/SQL compiler (ACPL) expected the next word to be the

name of a command. The command name must follow these keywords:
the DEFINE COMMAND keywords in the DEFINE COMMAND
section
the SET COMMAND keywords in the SET COMMAND statement
Correction
8693
Explanation
Find the DEFINE COMMAND section or the SET COMMAND statement

that is missing the command name and write in the command name. For
more information about using the DEFINE COMMAND section and the
SET COMMAND statement, see

.
ACPL ERROR: A string constant was expected.
The ACCELL/SQL compiler (ACPL) expected the next word to be a

string constant. The string constant must follow these keywords:
the ACTION IS, FIND_ACTION, or AUD_ACTION keywords in a
DEFINE COMMAND section
the LABEL IS, FIND_LABEL, or AUD_LABEL keywords in a
DEFINE COMMAND section
the KEY IS or KEYS ARE keywords in a DEFINE COMMAND
section
Correction
8694
Explanation
Correction
Find the statement with the missing string constant and rewrite the
statement. For more information about using the DEFINE COMMAND
section, see

.
ACPL ERROR: Illegal command action attribute value.
The ACCELL/SQL compiler (ACPL) found an invalid action specifier

(enable_string) value while parsing the DEFINE COMMAND section.
The valid action specifier values are the ENABLED or DISABLED
strings.
Find the DEFINE COMMAND section that has the invalid action
specifier and rewrite the specifier. For more information about action
specifiers in the DEFINE COMMAND section, see

.
75
8695
Explanation
Correction
8696
ACPL ERROR: Bad timer function declaration.
The ACCELL/SQL compiler (ACPL) found an invalid number of

parameters in the timer event handler function declaration. A Timer
function requires one non-result parameter.
Find the timer function declaration and rewrite it with one non-result
parameter. For more information about declaring a timer event handler
function, see

and

.

ACPL ERROR: Timer functions must be global and declared in
EXTERN statements.
Explanation
The ACCELL/SQL compiler (ACPL) found a timer event handler function

that is not global. The name of a global timer function must follow the
USING TIMER HANDLER clause of the CREATE TIMER EVENT
statement.
Correction
Declare the timer function globally with an EXTERN statement before it

is referenced in an ACCELL/4GL script. For more information about
creating and declaring timer events, see

and

.
8697
Explanation
ACPL ERROR: Invalid timer function reference.
The ACCELL/SQL compiler (ACPL) found an invalid timer function

reference. Invalid timer function references occur in these cases:
A timer function was called by just using the format
function_name(parameter).
A timer function was declared as a local function.
Correction
Try one or more of these solutions:

Find the timer function call and rewrite the call by using the
CREATE TIMER EVENT statement before referencing the timer
function.
Make sure that the timer function declaration uses the EXTERN
ACCELL TIMER statement. For more information about creating
and declaring timer events, see

and

.
76
8698
Explanation
ACPL ERROR: A TIMER keyword was expected.

TIMER keyword. The TIMER keyword must follow these keywords:
the CREATE keyword in a CREATE TIMER EVENT statement
the DELETE keyword or DELETE ALL keywords in a DELETE
TIMER EVENT statement
the USING keyword in a CREATE TIMER EVENT statement
Correction
8699
Explanation
Find the ACCELL/4GL statement that is missing the TIMER keyword

and rewrite the statement. For more information about creating and
deleting timer events, see

and

.
ACPL ERROR: An EVENT keyword was expected.

EVENT keyword. The EVENT keyword is required:
after the keyword TIMER in a CREATE TIMER EVENT statement
after the keyword TIMER in a DELETE TIMER EVENT statement
Correction
8700
Explanation
Find the ACCELL/4GL timer statement that is missing the EVENT

keyword and rewrite the statement. For more information about creating
and deleting timer events, see

and

.
ACPL ERROR: An EVENTS keyword was expected.

EVENTS keyword. The EVENTS keyword is required after the following
keywords:
the TIMER keyword in a DELETE ALL TIMER EVENTS
statement
the ALL or FOR keyword in an INSTALL statement
Correction
Find the ACCELL/4GL statement that is missing the EVENTS keyword

and rewrite the statement. For more information about installing and
deleting timer events, see

and

.
77
8701
Explanation
Correction
8702
Explanation
ACPL ERROR: Number of seconds for timer event was expected.
The ACCELL/SQL compiler (ACPL) expected the next word to be a valid

floating point expression for the number of seconds. The expression is
required after the IN keyword in the CREATE TIMER EVENT statement.
Find the CREATE TIMER EVENT statement and rewrite it with a valid
floating point expression for the number of seconds. For more
information about creating timer events, see

and

.
ACPL ERROR: The HANDLER keyword was expected.

HANDLER keyword. The HANDLER keyword is required after these
keywords:
the TIMER keyword in the USING TIMER HANDLER clause of
the CREATE TIMER EVENT statement
the DBMS_ERROR keyword in the INSTALL statement
Correction
8703
Explanation
Find the CREATE TIMER EVENT or INSTALL statement that is missing

the HANDLER keyword and rewrite the statement. For more information
about creating timer events, see

and

.
ACPL ERROR: A COMMAND keyword was expected.

COMMAND keyword. The COMMAND keyword is required:
after the DEFINE keyword in a DEFINE COMMAND statement
after the QUEUE keyword in a QUEUE COMMAND statement
after the CLEAR keyword in a CLEAR COMMAND QUEUE
statement
Correction
78
Find the ACCELL/4GL statement that is missing the COMMAND

keyword and rewrite the statement. For more information about defining
commands, see Defining and Executing Commands in this manual. For
more information about timer events and command queues, see

and

.
8704
Explanation
Correction
8705
Explanation
Correction
8706
Explanation
Correction
ACPL ERROR: A QUEUE keyword was expected.

keyword QUEUE. The QUEUE keyword is required after the keyword
COMMAND in a CLEAR COMMAND QUEUE statement.
Find the ACCELL/4GL statement that is missing the QUEUE keyword
and rewrite the statement. For information about queueing commands,
see

and

.
ACPL ERROR: A command name was expected.

name of a command. The command name is required after the QUEUE
COMMAND keywords in a QUEUE COMMAND statement.
Find the QUEUE COMMAND statement that is missing the command
name and rewrite the statement. For more information about queueing
commands, see

and

.
ACPL ERROR: A timer function name was expected.

name of a timer function. An ACCELL/SQL timer function must be
declared in the EXTERN ACCELL TIMER statement before being
referenced. The timer function name is required in the CREATE TIMER
EVENT statement.
Find the CREATE TIMER EVENT statement with the missing timer
function name and rewrite the statement or rewrite the EXTERN
declaration if that is wrong. For more information about creating and
declaring timer events, see

and

.
79
8707
ACPL ERROR: A timer function must be an ACCELL/SQL function.
Explanation
The ACCELL/SQL compiler (ACPL) found a timer function that is not

valid. An ACCELL/SQL timer function must be declared in the EXTERN
ACCELL TIMER statement before being referenced.
Correction
Make sure that all ACCELL/SQL timer functions are global and declared
in an EXTERN ACCELL TIMER statement. For more information about
creating and declaring timer events, see

and

.
8708
Explanation
ACPL ERROR: Operation cannot be performed on this command.

ACCELL/SQL compiler (ACPL) found a command name that poses one
of these problems:
The command name appears after the SET COMMAND keywords

in a SET COMMAND statement, but the command cannot be set.
The command name appears after the QUEUE COMMAND
keywords in a QUEUE COMMAND statement, but the command
cannot be queued.
Correction
8709
Explanation
Correction
Find the SET COMMAND or the QUEUE COMMAND statement that has
the problem command name and rewrite the statement using a valid
command name. For more information about using the SET COMMAND
statement, see Defining and Executing Commands in this manual. For
more information about the QUEUE COMMAND statement, see

and

.
ACPL ERROR: command_name: Command not defined.
The ACCELL/SQL compiler found an invalid command name in either a

SET COMMAND or a QUEUE COMMAND statement. The command
name must be either a command that is defined on this form or the name
of a valid ACCELL/SQL command.
Change the command name to a valid user-defined command name or an
ACCELL/SQL command. For information about defining commands, see

. For information about using the
DEFINE COMMAND section and the SET COMMAND statement, see

.
80
8710
Explanation
Correction
ACPL ERROR: Duplicate button attribute clause.

compiler (ACPL) found duplicate BUTTON clauses in a
DEFINE COMMAND section.
Make sure that you have only one BUTTON clause in each DEFINE
COMMAND section. Decide which of the BUTTON clauses you want
and include only that clause. Because the button clauses are mutually
exclusive, only one is allowed. For information about using the DEFINE
COMMAND section and the BUTTON clause, see

.
8712
Explanation
Correction
8713
Explanation
ACPL ERROR: A USERMENU keyword was expected.

compiler (ACPL) expected the USERMENU keyword.
This error can occur when the BUTTON clause of the DEFINE
COMMAND code section expects the USERMENU keyword to follow
the ON keyword.
Make sure that you are using the BUTTON clause correctly. For
information about using the DEFINE COMMAND section and the
BUTTON clause, see

.
ACPL ERROR: A button option was expected.

compiler (ACPL) expected one of the button options. This
error can occur when the BUTTON clause of the DEFINE COMMAND
section expects an option.

After the BUTTON keyword, the LOCATION and IS keywords are
optional. At that point a button option is expected.
Correction
Make sure that you are using one of the valid button options:
ON USERMENU
NOT ON USERMENU
AT (row, col)
For information about using the DEFINE COMMAND section and the
BUTTON clause, see

.
81
8714
Explanation
Correction
8715
Explanation
Correction
8716
Explanation
Correction
8717
Explanation
ACPL ERROR: The [ token was expected.
Either an array definition or reference is being used where a left bracket

is expected. In an array definition, if the LIST or MATRIX keyword is
used before an identifier, the compiler expects the array dimensions after
the identifier. Array references, in most cases, need subscripts enclosed
in brackets after the array identifier.
Enclose the array dimensions or array subscripts in brackets.
ACPL ERROR: The TO keyword was expected.
Array dimensions define the lower and upper bounds for an array. The
lower and upper bounds must be separated by the TO keyword, for
example, MATRIX array_name[1 TO 10], where 1 is the lower bound
and 10 is the upper bound.
Separate the lower and upper bounds of the array definition with the TO
keyword.
ACPL ERROR: The ] token was expected.
An array reference or definition has a left bracket, but no closing right

bracket.
Close the array reference or definition with a right bracket.
ACPL ERROR: The [ token was unexpected.
An array reference was followed by a colon and another array reference,

for example:
SET array_name[1]:array_name[2] TO 1
This syntax is not allowed by the compiler.

Correction
8718
Explanation
Correction
82
Change the statement to use valid array reference syntax.

ACPL ERROR: Array redefined.
An array has been defined more than once in an LOCAL statement.

Remove the incorrect array definition.
8719
ACPL ERROR: Invalid array dimension type.
When defining an array in a LOCAL statement, the array dimension

expressions must resolve to a numeric type.
Correction
8720
Change the dimension expression to be a numeric.
ACPL ERROR: REF parameters cannot be passed to Chooks or
system functions.
Explanation
Correction
8721
Explanation
Correction
8722
Reference parameters can be passed to ACCELL/SQL local and global

functions only. Attempting to pass reference parameters to any other type
of function (Chooks, ACCELL/SQL system functions, stored
procedures) results in an error.
Remove the reference parameter from the function definition.
ACPL ERROR: Invalid number of dimensions.
The number of dimensions specified in an array reference or definition

do not match the number of array dimensions specified in a FIELD [LIST
| MATRIX] statement.
Modify the FIELD [LIST | MATRIX] statement or the array reference or
definition so that the two specify the same number of dimensions.
ACPL ERROR: The LIST or MATRIX keyword was expected.
Explanation
A FIELD [LIST | MATRIX] statement declares a scalar (non-array) field

variable for an identifier that has been previously used to reference an
array.
Correction
Modify the references to the identifier so that they are used as only scalar
references or only array references.
83
8724
Explanation
ACPL ERROR: Invalid context for SELF.
A array self reference (array_name[ ]) was made outside that arrays

FIELD event section. Self references reference the current screen arrays
cell.
Correction
For screen array references that are not used in that arrays FIELD event
section, use explicit array subscripts. The subscripts fo the current screen
array cell can also be referenced by using the COL_INDEX,
ROW_INDEX, and LIST_INDEX array attributes. The following two
array references reference the same array cell:
array_name[ ]
array_name[array_name:ROW_INDEX, array_name:COL_INDEX]
8725
Explanation
Correction
8726
Explanation
Correction
8727
Explanation
Correction
84
ACPL ERROR: A REFERENCE parameter was expected.
A function call to a local or global function that takes a reference

parameter is being passed an invalid object as a reference parameter.
Scalar (non-array) or array variables may be passed to local or global
functions as reference parameters. Individual array cells may not be
passed as reference parameters.
Replace the invalid reference parameter. If the reference parameter is an
array cell, change the function to receive an array reference parameter
and pass the entire array.
ACPL ERROR: A LIST array name was expected.
A function call to a local or global function that takes a list reference

parameter is being passed something other than a list. Individual array
cells may not be passed as reference parameters.
Replace the offending parameter with a list array reference or change the
parameter type in the function declaration.
ACPL ERROR: A MATRIX array name was expected.
A function call to a local or global function that takes a matrix reference

parameter is being passed something other than a matrix. Individual array
cells may not be passed as reference parameters.
Replace the parameter with a matrix array reference or change the
parameter type in the function declaration.
8728
Explanation
Correction
8729
ACPL ERROR: Invalid syntax for array attribute.
An attempt was made to reference an array attribute with a scalar

variable, or a LIST attribute with a MATRIX array variable, or a
MATRIX attribute with a LIST array variable.
Change either the attribute or the variable so that they match.
ACPL ERROR: An array attribute was not expected.
Explanation
An attempt was made to use an array attribute with an identifier that has
been used as a non-array object.
Correction
If it is an array that is being referenced, make sure that it has been

defined correctly and that it has not been incorrectly reference earlier in
the script.
8730
ACPL ERROR: Invalid array dimensions.
Explanation
The dimensions of an array definition in a LOCAL statement are invalid.

Either one of the dimensions is undefined or the lower dimension is
greater than the upper dimension.
Correction
Make sure that each expression used as an array dimension evaluates to a

defined numeric value and that the lower dimension is less than or equal
to the upper dimension.
8731
Explanation
Correction
ACPL ERROR: Array dimensions were not expected.
An array subscript was used in an array reference where it is not needed

or valid. The array subscript is not valid when referencing the
DIMENSION array attribute. Subscripts cannot be used for variables that
have been used as scalar (non-array) variables in the script.
If the script references the DIMENSION array attribute, remove the
subscripts. If the script is referencing a scalar variable with array
attributes, the reference needs to be rewritten.
85
8732
ACPL ERROR: Array subscript was out of bounds.
Explanation
One of the subscripts of an array reference was out of bounds. The

compiler can check for out-of-bound references only for local arrays that
are defined in one of the scripts LOCAL statements. Also, when using
unbounded arrays, only the first dimension is unbounded. Thus, the
compiler checks for out-of-bound references on the second dimension of
bound as well as unbounded matrix arrays.
Correction
The first dimension of arrays can be referenced beyond the upper bounds
if the array is explicitly defined as an unbounded array by using the
UNKNOWN keyword when defining the upper bound of the arrays first
dimension. If the reference is correct, then expand the array dimensions
in the array definition in the LOCAL statement.
8733
ACPL ERROR: Invalid array reference.
Explanation
An attempt was made to reference an array without subscripts when not

allowed, for example, attempting to pass an array without subscripts to a
function as a value or result parameter.
Correction
If the intent was to reference an entire array, try using a FOR loop that
references each cell of the array. If the intent was to pass an entire array
to a local or global function, pass the array as a reference parameter.
8735
Explanation
Correction
ACPL ERROR: The LIST or MATRIX keyword was expected.
An array is defined in a LOCAL statement, and the LIST or MATRIX

keyword has been omitted.
When you declare an array in a LOCAL statement, the array name must
be preceded by the arrays type, LIST or MATRIX, for example:
LOCAL LIST array_list[1 TO 10],
MATRIX array_matrix[1 TO 10, 1 TO 10]
8736
Explanation
Correction
86
ACPL ERROR: Invalid array subscript.
A list array was referenced with two subscripts, or a matrix array was
referenced with one subscript.
Make sure that the array reference uses the correct number of subscripts.
8737
Explanation
Correction
8738
ACPL ERROR: A form attribute was not expected.
An attempt was made to use a form attribute with an array.

When referencing form attributes, the form attribute should follow the
form name and a colon.
ACPL ERROR: The FORMS or FUNCTIONS keyword was
expected.
Explanation
The REQUIRED keyword was not followed by the FORMS or

FUNCTIONS keyword, as expected.
Correction
Add the FORMS or FUNCTIONS keyword after REQUIRED.
8739
Explanation
ACPL ERROR: Database privilege expected.
A privilege keyword must always be specified following the GRANT or

REVOKE keyword.
Correction
8740
Explanation
Specify one of the following privileges to be granted or revoked: ALL

PRIVILEGES, DELETE, REFERENCES, USAGE, INSERT
(column_name), SELECT (column_name), or UPDATE (column_name).
ACPL ERROR: Database object name expected.
A database object name was expected following the ALTER CREATE, or

DROP keyword.
Correction
8741
Explanation
Correction
Specify one of the following database objects: TABLE, SCHEMA or

VIEW.. The VIEW keyword cannot be used in an ALTER statement.
ACPL ERROR: Invalid SQL command.
The specified SQL statement is invalid or nonstandard.

If the syntax of the SQL statement is invalid, correct the statement and
recompile the script. Otherwise, if the statement is not standard SQL, use
the BEGIN_SQL and END_SQL statements to enclose the statement.
These delimiters allow ACCELL/SQL to process SQL statements not
normally recognized by ACCELL/SQL but supported by the RDBMS.
87
8742
Explanation
Correction
8743
Explanation
Correction
8744
Explanation
Correction
ACPL ERROR: System Error.
This is an internal error and should not occur in the normal compiling of
an ACCELL/4GL script.
If this error occurs, please call Customer Support.
ACPL ERROR: Missing SQL statement terminator.
The end of the file was found before a semicolon terminating the current
statement. All SQL statements not enclosed in a BEGIN_SQL/END_SQL
block must be terminated with a semicolon. Note, however, that a SET . .
. SELECT statement that contains an executing block does not require a
semicolon.
Add a semicolon to the end of the appropriate statement.
ACPL ERROR: Statement must be within an executing block.
The UPDATE SELECTED ROW and DELETE SELECTED ROW

commands can be used only in the EXECUTING block of a SET . . .
SELECT statement.
To update or delete a record that was not retrieved by using a SET . . .
SELECT statement use the SQL UPDATE or DELETE statement. To
update or delete the current record in the selected set use the UPDATE
CURRENT RECORD or DELETE CURRENT RECORD command.
Use the UPDATE SELECTED ROW or DELETE SELECTED ROW
statement, if supported by the RDBMS, only to alter records that have
first been selected by using a SET . . . SELECT statement. The UPDATE
SELECTED ROW or DELETE SELECTED ROW statement must always
be used in the EXECUTING block in a SET . . . SELECT.
88
8745
ACPL ERROR: Illegal command on nonupdateable table or view.
Explanation
The UPDATE SELECTED ROW and DELETE SELECTED ROW

commands can be used only to modify updateable tables, and only if
supported by the RDBMS. In the SET . . . SELECT statement that
contains the EXECUTING block with the UPDATE SELECTED ROW or
DELETE SELECTED ROW statement, either the table specified is not
updateable, or several tables are specified in the FROM clause.
Correction
If a single table is specified in the SELECT statement, verify that the

permissions on the table allow the current user to perform updates and/or
deletes. If several tables are listed in the FROM clause, write separate
SQL UPDATE or DELETE statements to modify the individual tables.
If a view is specified in the FROM clause and that view is built from
several base tables, then separate SQL UPDATE or DELETE statements
must be written for each of the base tables.
8746
ACPL ERROR: The number of set variables and selected columns do
not match.
Explanation
Correction
8747
Explanation
Correction
The ACCELL/SQL compiler (ACPL) found a SET statement and SELECT

clause in which the number of variables in the variable list does not
match the number of column names in the database column list.
Find the SET statement and SELECT clause in which the lists do not
match, and rewrite the statement. See

for the syntax and usage of the SET and SELECT
statements.
ACPL ERROR: No FROM clause in SELECT statement.
The FROM clause is missing from a SELECT statement.

Add a FROM clause, with an appropriate table, to the SELECT statement
and recompile the script.
89
8750
Explanation
ACPL ERROR: The FILE keyword was expected.
The ACCELL/SQL compiler expected the next token to be the FILE

keyword. The FILE keyword is required in these cases:
after the TO keyword in the STORE statement
after the FROM keyword in the RETRIEVE statement
Correction
8751
Explanation
Correction
8759
Explanation
Correction
8760
Find the STORE or RETRIEVE statement that is missing the FILE

keyword and rewrite the statement. For the syntax for these
ACCELL/4GL statements, see

.
ACPL ERROR: Invalid data type specified for RETRIEVE statement.
The RETRIEVE statement simply reads TEXT or BINARY values from

files. The ACCELL/SQL compiler expected the next token to be either the
TEXT keyword or the BINARY keyword.
Find the RETRIEVE statement that is missing the TEXT or BINARY
keyword and rewrite the statement. For the syntax for the RETRIEVE
statement, see

.
ACPL ERROR: Old style database column name, remove #.
Release 2.0 of ACCELL/SQL does not allow the pound sign (#) before
database column names.
Remove the pound sign prefix from all database column names. Within
an SQL statement, ACCELL/SQL variables must be preceded by a dollar
sign ($), and database column names must not have any prefix.
ACPL ERROR: Clear to Add/Find expressions cannot be set using
set/select.
Explanation
Correction
90
Because clear-to-find and clear-to-add expressions are not evaluated until

the corresponding command is issued, the CLEAR_FIND_EXP and
CLEAR_ADD_EXP attributes cannot be set using a SET/SELECT
statement. Only simple SET statements may be used when setting these
attributes.
To achieve the same results as setting a CLEAR_FIND_EXP attribute
from a SELECT statement, use this technique:
In the ON CLEAR TO FIND section set a general variable to the value

returned by a SELECT statement; then SET the CLEAR_FIND_EXP
attribute to the value of the variable, for example:
ON CLEAR TO FIND
SET tmp_id TO SELECT id FROM id_table;
SET emp_id:CLEAR_FIND_EXP TO tmp_id;
Because clear-to-find expressions are evaluated immediately after the ON

CLEAR TO FIND section is executed, the attribute must be set in the ON
CLEAR TO FIND section. Any change to the value of tmp_id will
change the value that is assigned to emp_id.
A similar technique can be used to set a CLEAR_ADD_EXP attribute in
the ON CLEAR TO ADD section.
8761
ACPL ERROR: Clear to Add/Find expressions cannot be used in
nested set statements.

Explanation
Correction
8762
Explanation
Correction
Because clear-to-find and clear-to-add expressions are not evaluated until

the corresponding command is issued, CLEAR_FIND_EXP and
CLEAR_ADD_EXP attributes cannot be set within a nested SET
statement. Only simple SET statements may be used when setting these
attributes.
Divide the nested SET statement into several simple SET statements.
ACPL ERROR: EXECUTING clause can only be used with a

ROW_VALUED stored procedure.
An EXECUTING block can be used as part of a SET statement only if

the stored procedure called by the SET statement is ROW_VALUED.
NUMERIC stored procedures cannot be used with an EXECUTING
block.
Check the EXTERN for the referenced stored procedure to ensure that it
is correctly defined. Remove the EXECUTING block if the stored
procedure is correctly defined as NUMERIC. Otherwise, redefine the
procedure as ROW VALUED.
91
8763
ACPL ERROR: Number of user functions exceeds maximum allowed.
Explanation
The form script contains too many developer-defined functions. A single

form script can include up to 1,000 developer-defined functions.
Correction
8765
Reduce the number of functions in the form script.

ACPL ERROR: ACCELL/SQL objects may not be used in a DDL
command.
Explanation
Correction
8769
Explanation
ACCELL/SQL objects, such as variables and functions, cannot be used in

the text of a SQL DDL command. The following commands are
considered DDL commands: GRANT, REVOKE, CREATE, DROP, and
ALTER.
Rewrite the DDL statement so that it contains no ACCELL/SQL objects.

ACPL ERROR: Too many characters in a single token.
Explanation token strings can be up to 255 characters. The single

quotation marks that delimit the string constant are counted toward the
255 maximum, as shown in the following diagram.
1 character

1 character
Up to 253 characters
Correction
8772
If you must create a string constant of more than 253 characters, use the
string concatenation operator (+) to combine several shorter strings.
ACPL ERROR: Type returned does not match function definition
return type.
92
Explanation
The ACCELL/SQL compiler (ACPL) found a conflict between the return

type defined for a function and the value returned by the function. This
can occur if a function defined as returning a type of VOID contains a
RETURN statement that returns a value.
Correction
Either change the return data type defined for the function in the
FUNCTION statement to match the type that is returned or change the
statements that make up the function body so that a correct type value is
returned.
ACCELL/Manager (AMGR) Error

Messages
The following messages may be displayed while you are using
ACCELL/M anager to execute an application.
8800
Explanation
Correction
8801
Explanation
Correction
There are no errors to report.

An operation internal to ACCELL/M anager or ACCELL/ Generator has
completed successfully. If an ACCELL/SQL executable reports this error,
an internal error has occurred.
There is not enough memory to activate the form.
ACCELL/M anager ran out of memory while activating a form.
Try one or more of these alternatives:

Limit the use of the CONTINUE TRANSACTION transaction level
in your application.
Reduce the size or complexity of the form.
Increase the heap size or stack block size with the AMGR_HPSZ or
AMGR_STK_B_SZ configuration variables.
As a last resort, the system administrator can reconfigure the
memory parameters of your operating system.
8802
Explanation
The file is not in the proper format.

An ACCELL/SQL file has an unrecognizable magic number. Every
ACCELL/SQL file type has an associated magic number that enables
executables to distinguish between different types of files.
This error occurs when an ACCELL/SQL executable reads a file for which
the magic number does not match the type of file that was expected. The
file may have been corrupted or the user may have made an execution
error.
Correction
Run the appropriate ACCELL/SQL executable to generate the file again,

or recover the file from a backup.
ACCELL/SQL Manager (AMGR) Error Messages
93
8803
Explanation
Correction
8804
Explanation
Correction
There has been an internal system error.

An internal error has occurred while running ACCELL/M anager or
ACCELL/G enerator.
This error may result from exhausted resources or an internal program
error. In such a case, try different form script statements to achieve the
same result. If the error persists, call Unify Customer Support.
There is not enough memory to continue processing.

ACCELL/M anager or ACCELL/ Generator has run out of memory.

8805
Explanation
User has improper permission to access the file.

ACCELL/M anager or ACCELL/ Generator tried to access a file that the
current user did not have permissions to access.

Correction
8806
Explanation
Correction
94
Check the file permissions and correct them if needed.
There has been an I/O error detected by the system.

The operating system has detected a hardware error in the I/O subsystem.
Check the file system and repair or recreate it if needed. Hardware
diagnostics may further define a specific hardware problem. You may
also need to back up application files.
8807
Explanation
Correction
8808
There are too many active windows.

The number of currently active windows has exceeded the size of
ACCELL/M anagers internal tables.
Increase the number of windows allowed by the AMGR_NUM_WDWS
configuration variable. You can also modify the application to decrease
the number of windows displayed on the screen at one time.
The form cannot be displayed at the specified location.
Explanation
ACCELL/M anager could not display a form at the specified location. This
error can occur when a form script statement, such as DISPLAY TRIM,
gives invalid row and column coordinates for your terminal. This error
can also occur if a valid row and column location did not leave enough
room for the form to be displayed.
Correction
Determine which form script statement caused the problem and make
sure that the row and column coordinates specified are valid for the
terminal and the size of the form. If needed, adjust the size of the form or
its specified display location.
8809
Explanation
Correction
The specified form cannot be found in the form archive.

ACCELL/M anager could not find a form in an archive file.
Make sure that you are using the correct archive file. To make sure the
specified form exists in the form archive, add the form to the archive and
rebuild the application. Use ACCELL/E nvironment or the ACMB utility
to add the form to the archive.
Tip
You can create an application by using either of two methods:
by executing menu options in ACCELL/E nvironment
by executing ACCELL/SQL application development utilities
(AGEN, ACPL, ACMB, and ALNK) at the operating system
command-level
Do not mix the two application development methods.
ACCELL/E nvironment keeps track of form and file names that are created
through ACCELL/E nvironment, but cannot track forms and files created
by utilities.
95
8810
Explanation
An arithmetic overflow has occurred in a code section of the current

form.
ACCELL/M anager was converting a value from one ACCELL/SQL type to
another. During this conversion, arithmetic overflow occurred.

Correction
Determine whether the conversion problem was caused during user input
or during execution of a form script statement.
If the error was caused by user input, make sure that users do not
enter values that would overflow by changing the form script to
prohibit such input.
If the error was caused by a form script statement, change the
statement to prevent the conversion of values that could cause
overflow.
8811
An arithmetic underflow has occurred in a code section of the

current form.
Explanation
ACCELL/M anager was converting a value from one ACCELL/SQL type to

another. During this conversion, an arithmetic underflow occurred.
Correction
Determine whether the conversion problem was caused during user input
or during execution of a form script statement.
If the error was caused by user input, make sure that users do not
enter values that would underflow by changing the form script to
If the error was caused by a form script statement, change the form
script to prevent the conversion of values that could cause
underflow.
8812
Explanation
96
The specified value is not in a correct DATE format.

The DATEFMT configuration variable determines the current date format
displayed in ACCELL/SQL applications. This error occurs when
ACCELL/M anager finds an invalid date value represented as a string. For
example, the date value 30/12/88 is invalid for the date format
MM/DD/YY, because 30 is not a valid month.
Correction
Make sure that the DATEFMT configuration variable is set correctly.

Determine whether the invalid value was caused by user input or during
execution of a form script statement.
If the error was caused by user input, make sure that the user does
not enter invalid date values by changing the form script to
If the error was caused by a form script statement, change the
statement to prevent invalid DATE values.
The DATEFMT configuration variable is described in

.
8813
Explanation
The current operation requires more heap memory than available.

ACCELL/M anager keeps a variety of internal information in an area
called the heap. The current heap size is too small to run the current
application.
Correction
8814
Explanation
Correction
Increase the heap size by changing the AMGR_HPSZ configuration

variable. This configuration variable is described in

.
The specified file cannot be found.
ACCELL/M anager or ACCELL/ Generator could not find the specified file.
Make sure that the specified file exists and that the current user has read
access for the file.
Also, make sure that the following configuration variables are set
correctly: UNIFY, ACLPATH, ACLENV, and APPMAP. These configuration
variables are described in
.
8815
Explanation
The data types for this operation do not match.

ACCELL/M anager was performing an operation that required operands
with matching data types and found an invalid type. Operations likely to
cause this problem are assignments of a value or an attribute and
arithmetic operations, such as addition and multiplication.
97
Correction
8816
Explanation
Correction
8817
Find the offending form script statement and change the statement so that
only correct data types are used in the operation. For more information
about operator compatibility, see

.
The values data type is incorrect for this operation.

ACCELL/M anager was performing an operation that required compatible
data types and found an invalid type. Operations likely to cause this
problem contain arithmetic, relational, or bitwise operators.
Find the offending form script statement and change the form script
variables so that only correct data types are used in the operation. For
more information about operator compatibility, see

.
A division by zero is not allowed.
Explanation
ACCELL/M anager found a form script statement that tried to divide by

zero. This is an invalid arithmetic operation.
Correction
Find the form script statement that caused the problem and change the
statement so that it does not divide by zero.
8818
Explanation
Correction
The help form archive file cannot be found.

ACCELL/M anager could not open the archive for the help form
associated with the current field or specified by the DISPLAY HELP
statement.
Make sure that the help form archive file exists and that the current user
has read access to the file. Help form archive names for fields are
specified on the Form Definition and Field Definition forms in
ACCELL/ Generator.
Also make sure that the UNIFY, ACLPATH, and ACLENV configuration
variables are set correctly. For more information about these
configuration variables, see

.
98
8819
Explanation
Correction
8826
Explanation
Correction
8827
Explanation
The help form cannot be found in the help archive file.

ACCELL/M anager was attempting to display a help form and could not
find that form in the help archive.
Make sure that the current user has read permission for the file. Also
make sure that you are accessing the correct version of the help form
archive. Use ACCELL/ Generator to correctly define a help form for a
field.
The form referenced in the code section is not active.

ACCELL/M anager found a reference to a variable on a form that is not
the current form. Because the specified form was not active, the Manager
could not find the variable.
Make sure that the form name specified is spelled correctly. Also make
sure that all variable references include form names of forms that are
active when this section of form script is executed.
A reference has been made to a non-existent external symbol.

ACCELL/M anager found a reference to a variable that was specified as
being on a currently active form, but the referenced variable could not be
found on that form.
Correction
8828
Explanation
Correction
Make sure that the form name and variable name referenced are spelled
correctly and that the variable is used on the specified form. If necessary,
declare the variable on the current form.
The referenced ACCELL/SQL help file cannot be found or is not

readable.
ACCELL/M anager found an error while trying to read one of its own help
form archive files. These files are located in the directory specified by
the UNIFY configuration variable.
Make sure that the UNIFY configuration variable is set correctly. Make
sure that the file exists and that the current user has read permission for
the file. If necessary, restore the archive file from a backup.
99
8829
Explanation
ACCELL/M anager found an error while trying to read one of its help
subsystem files. These files are located in the directory specified by the
UNIFY configuration variable.
Correction
sure that the specified help subsystem file exists and that the current user
has read permission for the file. If necessary, restore the help subsystem
file from a backup.
8830
The referenced help form has too many next forms associated with
it.
Explanation
Correction
8831
Explanation
Correction
8832
100
The ACCELL/SQL help sub-system file cannot be found or is not

readable.
The number of next forms specified for a help form in an ACCELL/SQL

help subsystem exceeded the maximum. These files are located in the
directory specified by the UNIFY configuration variable.
Make sure that the UNIFY configuration variable is set correctly. If
necessary, restore the specified help description file from a backup.
The referenced help form cannot be found in the help description
file.
The help subsystem form must be referenced in the help description file
but was not. These files are located in the directory specified by the
UNIFY configuration variable.
Make sure that the UNIFY configuration variable is set correctly. If
necessary, restore the specified help description file from a backup.
A command sequence is linked to more than one command in the
unicap file.
Explanation
The unicap file currently maps more than one command to the same
command sequence in the same mode. For example, you would get this
error if you had assigned to both
and to

in find mode.
Correction
Make sure that each command sequence in the unicap file is assigned to
only one command per form mode. See your system administrator about
correcting the problem in the unicap file.
8834
Explanation
Correction
8835
Explanation
Correction
8836
Explanation
There are no records in the selected set.

You have entered a user command that requires a selected set, or
ACCELL/M anager tried to execute a form script statement, such as
CHANGE CURRENT RECORD, that requires a selected set.
Use the FIND or ADD/UPDATE commands to establish a selected set.
This is the last record.
ACCELL/M anager was already positioned on the last record in the
selected set when a NEXT RECORD , NEXT SET or LAST RECORD
command was entered to change the position in the selected set to a
following record.
See

for more information about
using record commands.
This is the first record.
ACCELL/M anager was already positioned on the first record in the
selected set when a PREVIOUS RECORD , PREVIOUS SET, or
FIRST RECORD command was entered to change the position in the
selected set to a preceding record.

Correction
8837
Explanation
Correction
8838
Explanation
Correction
See

This is the last set.
ACCELL/M anager was already positioned on the last set of the selected
set when a NEXT SET command was entered.
See

This is the first set.
ACCELL/M anager was already positioned on the first set of the selected
set when a PREVIOUS SET command was entered.
See

101
8839
Explanation
Correction
8840
The specified search criteria is invalid.

Search criteria has been specified that is not in the correct format.
See
specifying search criteria.
The justification specifier is invalid.
Explanation
Display justification can be LEFT, RIGHT, or CENTERED. Display

justifications are used in the DISPLAY statement and as values to the
DISPLAY_JUSTIFY screen attribute.
Correction
Find and correct the form script statement that contains the invalid
display justification. For the syntax and usage for the DISPLAY
statement and for information about the DISPLAY_JUSTIFY screen
attribute, see

.
8841
Explanation
The current record cannot be deleted.

ACCELL/M anager or ACCELL/G enerator tried to execute a

command, but the current record cannot be deleted
because the current form has no current record.

Correction
8842
Explanation
Correction
102
Use the command to establish a selected set and a current record.
See
using the
command.
Cannot open the application .al map file.

ACCELL/M anager could not open the application map file.
The application map file is created by the ACCELL/SQL linker. Make

sure that the correct file name was used, that the file exists, and that the
current user has the correct permissions for the file.
8843
Explanation
Correction
Cannot read the application .al map file.

ACCELL/M anager could not read the application map file.
The application map file is created by the ACCELL/SQL linker. Make

sure that the correct file name was used, that the file exists, and that the
current user has read permission for the file.
If the problem remains, the file may be corrupted. In this case, you must
rebuild the application map file by executing the ACCELL/SQL linker
(ALNK) or by using ACCELL/E nvironment, depending on the method
originally used to create the application.
You can also restore the file from a backup.
8844
Explanation
Correction
8845
Explanation
The unicap file could not be opened.

ACCELL/M anager could not open the specified unicap file. A valid
unicap file is required for ACCELL/M anager to execute.
Make sure that the UNIFY and UNICAP configuration variables are set
correctly. These variables are described in

. Also make sure that the ignoremiss entry
is correct in the unicap file. See

for more information about the unicap file.
There is no next form for this form.
ACCELL/M anager attempted to execute a command and
there was no next form to execute.

Correction
8847
Explanation
Correction
Check that the current form has Next forms defined. Next forms can be
defined within ACCELL/ Generator from the Choose Next Form form.
Next forms can be defined within ACCELL/ 4GL with the CHOOSE
NEXT FORM or CHOOSE FIRST FORM statements.
The referenced C-hook function cannot be found.
ACCELL/M anager could not find the C-hook function specified in the
form script.
Make sure that the function name is spelled correctly in the form script.
Also make sure that you have linked the C-hook function into the
Manager. See

about writing C-hook functions.
103
8848
Explanation
Bad heap size parameter: size.

ACCELL/ Generator or ACCELL/M anager found an invalid value for the
AMGR_HPSZ or AGEN_HPSZ configuration variable. The configuration
variable currently has the invalid value of size.

Correction
8849
Explanation
Correction
8850
Bad number of windows parameter: size.

The configuration variable AMGR_NUM_WDWS was set to an invalid
value of size.
Make sure that the AMGR_NUM_WDWS configuration variable is set to a
valid value. This variable is described in

.
Bad stack block size parameter: size.
Explanation
The configuration variable AMGR_STK_B_SZ was set to an invalid value

of size.
Correction
Make sure that the AMGR_STK_B_SZ configuration variable is set to a

valid value. This variable is described in

.
8852
104
Make sure that the AMGR_HPSZ and AGEN_HPSZ configuration variables

are set to valid values. These variables are described in

.
ACCELL/SQL is unable to open the error file file_name.
Explanation
Either ACCELL/M anager found an invalid value for the AMGR_ERFL

configuration variable, or ACCELL/ Generator found an invalid value for
the AGEN_ERFL configuration variable.
Correction
Make sure that the AMGR_ERFL and AGEN_ERFL configuration variables

are set to valid values. These variables are described in

. Also make sure the file
named file_name exists.
8853
Explanation
Correction
8854
Explanation
A reference has been made to an invalid screen field name.

ACCELL/M anager tried to reference a screen field that does not exist on
the specified form, or, if no form was specified, on any application form.
Determine which form script statement caused the error and make sure
that the statement uses a valid screen field name.
The referenced form is unknown to the Manager.

ACCELL/M anager tried to reference a form that was not linked in the
application. Either the form name is incorrect, or it was not listed in the
REQUIRED FORMS or REQUIRED FUNCTIONS clause and was not
found in any of the archives associated with the application. In the latter
case, the form has no entry in the application map file created by the
ACCELL/SQL linker.
Correction
Make sure that the form name is spelled correctly and is listed in one of
the following locations:
the REQUIRED FORMS or REQUIRED FUNCTIONS clause of
the master application form script
one of the archives specified in the ARCHIVES clause
the archive specified on the command line to ALNK
To make sure that the .al application map file is up to date, execute
ACCELL/SQL Linker (ALNK) or rebuild the application from
ACCELL/E nvironment.
8855
Explanation
Correction
The database design is different from when the application was

built.
When ACCELL/SQL builds an application, it uses information from the
current database design. This error occurs when information stored in the
application does not match the information currently in the database
design.
Make sure that the variables used by your RDBMS to find the database
are set correctly.
105
If you are using this RDBMS:
Then these variables must be set:
INFORMIX Online
INFORMIX SE
INGRES
ORACLE
SYBASE SQL Server
DSQUERY and SYBASE
Unify DataServer
DBPATH and DBNAME
You can also rebuild your application from scratch.
8857
Explanation
Some command definitions are missing from the unicap file.

ACCELL/M anager requires a complete unicap file to proceed. The
ignoremiss Boolean flag is set to FALSE, so that ACCELL/M anager
reports an error if any commands are missing from the sgl section of the
unicap file.
Correction
8858
The main help form is not in the help sub-system description file.
Explanation
ACCELL/M anager could not find the main help form listed in the help
subsystem description file. This file must be corrupt.
Correction
106
Make sure that the UNIFY and UNICAP configuration variables are set
correctly. These variables are described in

. Also make sure that the ignoremiss entry
is correct in the unicap file. See

for more information about the unicap file.
Recover the help subsystem description file from a backup.
8859
The current record could not be locked. Try again later.
Explanation
When changing the current record, ACCELL/M anager found a record that
was locked by another user. Because the record was locked,
ACCELL/M anager continued trying to find another record in the selected
set that it could lock.
Correction
Try moving to the record at a later time when the record may not be
locked. See ACCELL/SQL: Writing Form Scripts and ACCELL/SQL:
RDBMS Integration for more information about transactions and locking
in ACCELL/SQL .
8860
Explanation
Correction
8861
The referenced variable does not refer to a screen field.

A variable was used in a form script context that requires a screen
variable, but the variable is not a screen variable. For example, the
DISPLAY_FORMAT attribute must be used with a field variable.
Find the form script statement that caused the error and make sure that
the variable name refers to a valid screen field. See ACCELL/SQL:
Writing Form Scripts for more information about screen variables and
their attributes.
The referenced variable is not a target variable.
Explanation
A variable was used in a context that requires a target variable, but the
variable is not a target variable. For example the SEARCH_RANGES
attribute must be used with a target variable or target field variable.
Correction
Find the form script statement that caused the error and make sure that
the variable name refers to a database column in the target table. See
ACCELL/SQL: Writing Form Scripts for more information about target
and target field variables and their attributes.
8862
Explanation
Correction
A subtraction operation was attempted on a string value.

A form script statement tried to subtract a string value. Subtraction is not
allowed for strings.
Find the form script statement that caused the error and modify the
statement so that it does not try to subtract a string. See ACCELL/SQL:
Writing Form Scripts for more information about string values and the
subtraction operator.
107
8864
Explanation
All records in the selected set are locked by another user.

ACCELL/M anager could not establish a current record because all records
are locked.
Correction
8865
Explanation
Correction
8866
Explanation
Correction
8874
Try the search operation again later when the records in question might
not be locked. See ACCELL/SQL: Writing Form Scripts and
ACCELL/SQL: RDBMS Integration for more information about
transactions and locking in ACCELL/SQL .
The form name specified in an ERASE TRIM statement has not been
displayed.
An attempt was made to erase the trim of a form that has not yet been
displayed.
Find the ERASE TRIM that caused the error and make sure that the form
name is spelled correctly. Verify that this form has been displayed with a
DISPLAY TRIM statement. See ACCELL/SQL: Script and Function
Reference for the syntax and usage of the DISPLAY TRIM and ERASE
TRIM statements.
Trim does not exist.
An attempt has been made to display a form that has no trim.
Find the DISPLAY TRIM statement that caused the error and make sure
that the form name is spelled correctly, that the form exists, and that it is
defined correctly. See ACCELL/SQL: Script and Function Reference for
the syntax and usage of the DISPLAY TRIM statement.
A CREATE PIPELINE 4GL statement has failed.
Explanation
ACCELL/M anager could not establish a pipe between programs listed in

the CREATE PIPELINE statement.
Correction
Find the CREATE PIPELINE statement that caused the error and make
sure that all the programs in the program list exist, are executable,
operate correctly, and are on the directory search path specified by your
PATH configuration variable.
See ACCELL/SQL: Script and Function Reference for the syntax and
usage of the CREATE PIPELINE statement. See ACCELL/SQL: Script
and Function Reference for the syntax and usage of the CREATE
PIPELINE statement.
108
8875
Explanation
Correction
A CLOSE PIPELINE 4GL statement has failed.

ACCELL/M anager could not terminate the pipe listed in the CLOSE
PIPELINE statement.
Find the CLOSE PIPELINE statement that caused the error and make
sure that a CREATE PIPELINE statement has successfully executed for
this pipeline variable. Also make sure that the pipeline variables value
has not changed since the CREATE PIPELINE statement was executed.
See

using the pipeline statements. See

for the syntax and usage of the CREATE PIPELINE statement.
8876
The pipeline variable for a pipe must be of type NUMERIC.
Explanation
A pipeline variable does not have the correct data type. Because pipeline
variables contain operating system file descriptors that are integers,
pipeline variables must be of type NUMERIC.
Correction
If the error occurs on a CREATE PIPELINE statement, make sure that

the pipeline variable used is of NUMERIC data type or is UNDEFINED. If
the error occurs on a CLOSE PIPELINE statement, make sure that a
CREATE PIPELINE statement has successfully executed and that the
pipeline variable has not been modified since. The pipeline variable must
have a non-null numeric value.
See


8877
Cant create a CREATE PIPELINE output file.
Explanation
The CREATE PIPELINE statements OUTPUT IS clause has specified an

output file that cannot be created.
Correction
Make sure that the directory where the output file would reside exists and
that the current user has write permission on both the directory and the
file. Also, make sure that you have enough disk space to create the file.
See


109
8878
Explanation
Correction
8879
Explanation
Correction
8880
110
A CREATE PIPELINE statement program could not be executed.

ACCELL/M anager could not execute one of the programs in the program
list of a CREATE PIPELINE statement.
sure that all the programs in the program list exist, are executable,
operate correctly, and are on the directory search path specified by your
PATH configuration variable. See

for more information about using the pipeline statements. See

of the CREATE PIPELINE statement.
There has been an abnormal pipeline program termination.

ACCELL/M anager was able to establish a pipeline and execute the
pipeline programs but one of these programs terminated abnormally.
sure that all the programs specified in the CREATE PIPELINE statement
operate correctly. See

for more
information about using the pipeline statements. See

for the syntax and usage of the CREATE
PIPELINE statement.
Too many or no pipeline tasks have been started.
Explanation
ACCELL/M anager received an error from the operating system that

indicated that too many or no tasks have been started. This error occurs
during the execution of a CREATE PIPELINE statement.
Correction
Find the CREATE PIPELINE statement that caused the error and try
reducing the complexity of the CREATE PIPELINE statement. Also
consider using intermediate files. See

for more information about using the pipeline statements. See

of the CREATE PIPELINE statement.
8881
Explanation
Correction
8883
Explanation
An invalid display justification type was encountered.

Display justification can be LEFT, RIGHT, or CENTERED. Display
justifications are used in the DISPLAY statement and as values to the
Find and correct the form script statement that contains the invalid
display justification. See ACCELL/SQL: Script and Function Reference
for the syntax and usage of the DISPLAY statement and the
Bad arguments to 4GL system function.

ACCELL/M anager tried to execute a system function with incorrect
arguments.
Correction
8884
Explanation
Correction
Find the system function call that caused the error and make sure that the
system function is passed the correct number and types of arguments.
Also make sure that no undefined values are being passed as function
arguments. See ACCELL/SQL: Script and Function Reference for
information about the ACCELL/SQL system functions.
A master application forms NEXT FORM cannot continue a

transaction.
The user executed the command from the master
application form but this next form had a transaction level of
CONTINUE TX. The transaction level must be START TX for the next
form of a master application form.
Correct the next form definition(s) for the master application form. The
Next form for a master application form can be defined from the Choose
Next Form form in ACCELL/ Generator or with the CHOOSE FIRST
FORM form script statement in the master application form script.
See ACCELL/SQL: Writing Form Scripts and ACCELL/SQL: RDBMS
Integration for more information about ACCELL/SQL transactions and
locking. See ACCELL/SQL: Script and Function Reference for the
syntax and usage of the CHOOSE FIRST FORM statement.
111
8886
Value is undefined.
Explanation
ACCELL/M anager found an UNDEFINED value while trying to use a

display format. Display formats are used in the DISPLAY statement and
as values to the DISPLAY_FORMAT screen attribute.
Correction
Find and correct the form script statement that contains the undefined
value. See ACCELL/SQL: Script and Function Reference for the syntax
and usage of the DISPLAY statement and description of the
DISPLAY_FORMAT screen attribute. For more information about
display formats, see ACCELL/SQL: Localizing an Application.
8887
Explanation
An invalid variable or database type was detected.

ACCELL/M anager detected an invalid ACCELL/SQL or RDBMS data
type.
Correction
8894
Explanation
Correction
8895
112
Make sure that no C-hook function introduces an invalid ACCELL/SQL

or RDBMS data type. Make sure that ACCELL/SQL variable types match
the data types of their associated database columns in the INSERT,
SELECT, and UPDATE statements. See ACCELL/SQL: Writing Form
Scripts for more information about ACCELL/SQL data types. See
ACCELL/SQL: RDBMS Integration for more information about RDBMS
data types.
Invalid default justification.
When formatting a value for output, ACCELL/M anager found a default
display justification that was invalid. This is an internal error and should
not occur in the normal execution of an ACCELL/SQL application.
The screen field is not wide enough for the formatted value.
Explanation
When formatting a value, ACCELL/M anager or ACCELL/G enerator

determined that the value could not be formatted in the specified screen
field. Therefore, the value was truncated.
Correction
Make the screen field wider, the display format narrower, or do not
display values that are wider than the associated screen field. See
ACCELL/SQL: Developing an Application for more information about
display formats.
8897
Attempted an arithmetic operation with an old-style NULLDATE

value.
Explanation
NULLDATE is a keyword that represents a null DATE value in

applications developed under ACCELL 1.4 and earlier. One restriction on
NULLDATE values is that certain arithmetic operations, such as addition,
cannot be performed on them.
Correction
If you are using an older ACCELL application, find the form script
statement that contains the arithmetic operations on NULLDATE values
and eliminate arithmetic operations on NULLDATE values. Note that to
use older ACCELL applications with ACCELL/SQL , you must execute the
application in compatibility mode, with the CMPTFLG configuration
variable set to TRUE.
A better way to eliminate the problem is to convert your application so
that it does not execute in compatibility mode. In a converted
application, all references to the obsolete NULLDATE keyword must be
changed to the NULL keyword for DATE null values.
See Converting Applications to ACCELL/SQL and UNIFY 2000 and
ACCELL/SQL: Converting Release 1 Applications to Release 2 for
information about converting from earlier releases of ACCELL or
ACCELL/SQL .
8898
Explanation
Correction
8899
Explanation
Correction
The command entered is invalid in the current mode.

The last command entered was not in the set of valid commands for the
current mode. ACCELL/M anager has a set of valid commands for both
Find mode and Add/Update/Delete mode.
Make sure that the unicap file is correct. For information about the
unicap file, see ACCELL/SQL: Setting Up a User Environment. For
more information about valid commands in each mode, see
ACCELL/SQL: Using an Application.
The current field is required.
The form is in add/update mode and the current field must contain a
valid value before you can move to the next field or add or update the
record. Because the fields screen variable has the REQUIRED screen
attribute set to TRUE, a value must be entered when in add/update mode.
You must enter a valid value for the current field when it is a required
field.
113
8901
A referenced form is not active. The transaction cannot be restarted.
Explanation
The Next form definition has a transaction level of RESTART TX but the
requested Next form is not currently active. Transactions can only be
restarted to active forms.
Correction
Find out why the requested Next form is not active. You may need to
correct the Next form definition(s). Next forms can be defined from the
Choose Next Form form in ACCELL/ Generator or with the CHOOSE
NEXT FORM form script statement in a standard form script.
See ACCELL/SQL: Writing Form Scripts and ACCELL/SQL: RDBMS
Integration for more information about ACCELL/SQL transactions and
locking. See ACCELL/SQL: Script and Function Reference for the
syntax and usage of the CHOOSE NEXT FORM statement.
8902
Explanation
Correction
8903
114
There is an undefined boolean variable in a statement.

ACCELL/M anager was evaluating a boolean expression in a FOR,
WHILE, REPEAT, or IF statement, but the value was undefined.
Find the control statement that is causing the error and make sure that all
variables in the logical expression are defined. See ACCELL/SQL: Script
and Function Reference for the syntax and usage of the form script
control statements.
The CLEAR TO FIND command requires at least one searchable

field.
Explanation
The user executed the CLEAR TO FIND command, but no target fields
on the form have the STOP_FOR_INPUT screen attribute set to TRUE.
The CLEAR TO FIND command changes the form to find mode, in
which search criteria can be specified for the forms target table.
Correction
A target field variables STOP_FOR_INPUT field attribute should be set

to TRUE, or the CLEAR TO FIND command should not be allowed.
See ACCELL/SQL: Creating Screen Forms and ACCELL/SQL: Script
and Function Reference for more information about target field variables
and the STOP_FOR_INPUT screen attribute.
8905
Error in WRITE PIPELINE statement. Check operation of pipe

programs.
Explanation
A WRITE PIPELINE statement failed because one of the programs could

not be executed.
Correction
Make sure that all the programs in the pipeline exist, are on the directory
search path specified by your PATH configuration variable, and are
executable. Also, make sure that all the programs in the pipeline operate
correctly. See

about using the pipeline statements. See

for the syntax and usage of the WRITE PIPELINE
statement.
8906
Explanation
Correction
8907
Explanation
Correction
8908
Explanation
Wrong number of arguments in an ACCELL/SQL function call.

ACCELL/M anager tried to execute a user-defined form script function
with an incorrect number of arguments.
Find the form script function call that caused the error and make sure that
the function is spelled correctly and is passed the correct number of
arguments. See

for more
information about ACCELL/SQL form script functions.
There was a bad type involved in conversion.
ACCELL/M anager found an invalid data type when converting a value
from one ACCELL/SQL data type to another.
Make sure that no C-hook function introduced an invalid ACCELL/SQL

data type. See

about ACCELL/SQL data types and writing C-hook functions.
The specified value is not in correct TIME format.
ACCELL/M anager found a time value that was invalid. For example, the
string dog is an invalid time value, but the string 06:30 is valid if the
the TIMEFMT configuration variable is set to HH:MM .
Correction
Enter the time value in the correct format or change the offending form
script statement. See

for more
information about valid time values. For information about the TIMEFMT
configuration variable, see

.
115
8909
Explanation
ACCELL/M anager found a boolean value that was invalid. For example,
the strings dog is an invalid boolean value, but the strings YES and
n are valid boolean values if the the BOOLFMT configuration variable
is set to YES/NO.
Correction
Enter the boolean value in the correct format or change the offending
form script statement. See for
more information about valid boolean values. For information about the
BOOLFMT configuration variable, see

.
8910
The specified value is not in correct FLOAT format.
Explanation
ACCELL/M anager found a float value that was invalid. For example, the
strings 1/1/88 and $1.00 are invalid float values, but the strings
99.99 and 1.087 are valid float values. The display format for
FLOAT values can be specified by setting the FLTFMT configuration
variable.
Correction
Enter the float value in the correct format or change the offending form
script statement. See for more
information about valid float values. For information about the FLTFMT
configuration variable, see
.
8911
116
The specified value is not in correct BOOLEAN format.
The specified value is not in correct NUMERIC format.
Explanation
ACCELL/M anager found a numeric value that was invalid. For example,
the strings dog and 99.99 are invalid numeric values, but the strings
8 and 3557 are valid numeric values. The display format for
NUMERIC values can be specified by setting the NUMFMT configuration
variable.
Correction
Enter the numeric value in the correct format or change the offending
form script statement. See for
more information about valid numeric values. For information about the
NUMFMT configuration variable, see

.
8912
The specified value is not in correct AMOUNT format.
Explanation
ACCELL/M anager found an amount value that was invalid. For example,
the strings 1/1/88 and 1 are invalid amount values, but the strings
$99.99 and $1.0 are valid amount values. The display format for
AMOUNT values can be specified by setting the AMTFMT, CURRSYM ,
TRIADSEP, and RADIXSEP configuration variables.
Correction
Enter the amount value in the correct format or change the offending
form script statement. See ACCELL/SQL: Writing Form Scripts for more
information about valid amount values. For information about the
AMTFMT, CURRSYM , TRIADSEP, and RADIXSEP configuration variables,
see ACCELL/SQL: Configuration Variable and Utility Reference.
8913
Explanation
Correction
Could not open database.

ACCELL/M anager could not open the database.
Make sure that the correct application directory is current.

Make sure that the variables used by your RDBMS to find the database
are set correctly.
If you are using this RDBMS:
Then these variables must be set:
INFORMIX Online
INFORMIX SE
INGRES
ORACLE
SYBASE SQL Server
DSQUERY and SYBASE
Unify DataServer
DBPATH and DBNAME
Make sure that you have database access permission and that you have
read/write permission for the database files.
For Unify DataServer users only:
If the database has been shut down, you may not be able to open the
database. Make sure that the AUTOSTART and OWNERSTART
configuration variables do not prevent you from opening the database.
See UNIFY 2000: Configuration Variable and Utility Reference for
information about these variables.
117
8914
Explanation
Correction
8916
Explanation
Correction
8920
Explanation
Correction
8921
Explanation
Could not close database.

ACCELL/M anager could not close the database. This error indicates that
there is a problem with system resources or the operating system, or that
an internal ACCELL/SQL error has occurred.

Could not commit a transaction.
ACCELL/M anager could not commit the current transaction. This error
indicates that there is a problem with system resources or the operating
system, or that an internal ACCELL/SQL error has occurred.

Date initialization failed.
ACCELL/M anager could not initialize its internal date information. This
error indicates that there is a problem with system resources or the
operating system, or that an internal ACCELL/SQL error has occurred.

Operating system interrupt handler problem.
ACCELL/M anager found an operating system error in the interrupt
handler area. This error indicates that there is a problem with system
resources or the operating system, or that an internal ACCELL/SQL error
has occurred.
Correction
8922
The function key specified is not known to this form.
Explanation
ACCELL/M anager found a DEFINE COMMAND section or a SET

COMMAND statement that referred to a function key that is not known
to the current form. This is an internal error and should not occur in the
normal execution of an ACCELL/SQL application.
Correction
118

8930
Explanation
Correction
8931
Explanation
Internal problem with null values.

ACCELL/M anager or ACCELL/G enerator found an invalid null value.
Make sure that no C-hook function introduced an invalid null value. If

this is not the case, an internal ACCELL/SQL error has probably occurred;
please call Unify Customer Support.
The keyword NULL appears in an invalid ACCELL/4GL context.
Because the NULL keyword is a null value that has no associated data
type, there are restrictions on where it can occur in a script. Most of these
invalid contexts are caught by ACCELL/SQL Compiler (ACPL).
However, some instances cannot be caught until runtime by
ACCELL/M anager. In particular, ACCELL/M anager must catch an
assignment of the NULL keyword to an undefined general variable. Such
an assignment is invalid because the undefined general variable has no
data type associated with it.
Correction
8932
Find the form script statement that caused this error and make sure that
general variables are defined before assigning the NULL keyword to
them. For more information about null values, see ACCELL/SQL:
Writing Form Scripts.
Cannot switch to or obtain information on a schema.
Explanation
ACCELL/M anager could not switch to or get information about the

database object that contains the application files. This database object is
a database, owner, schema, or user, depending on the RDBMS on which
Correction
Make sure that you are using the correct database (or server for SYBASE
SQL Server) and that the database design used in your application
matches the current database design.
Also, make sure that the database, owner, schema, or user specified for
the application is correct and that the current user has the correct
permissions for running an application under that database, owner,
schema, or user. The database, owner, schema, or user is specified in
ACCELL/E nvironment or on the AMGR command line with the S
option.
See ACCELL/SQL: RDBMS Integration or your RDBMS manuals for
more information about databases, owners, schemas, or users.
119
8933
Explanation
Correction
8935
Explanation
Correction
8936
Explanation
Cannot obtain information on a user.

ACCELL/M anager could not get information about the current user from
the database.
Make sure that you are using the correct database and that the database
design used in your application matches the current database design.
Also, make sure that the current user has the correct permissions for
running an application under the specified database, owner, schema, or
user. See your RDBMS manuals for more information about user
information in the database.
Unused column accessed.
ACCELL/M anager was attempting to access a column that no longer
exists in the target table.
If a form is created in ACCELL/SQL for a target table, and later a

column is dropped from the table, then the form must be modified to
match the table.
Cannot open application database map file.
ACCELL/M anager could not open the file specified by the APPMAP
configuration variable. This variable specifies the file that contains

database directory search paths for accessing specific databases and
applications in application systems.
Correction
8937
Explanation
Make sure that the APPMAP configuration variable is set correctly. Also
verify that the user has the correct permission on the application database
map file. See ACCELL/SQL: Managing an Application for more
information about accessing databases and applications in application
systems.
The resultant string has overflowed the display format.
ACCELL/M anager or ACCELL/G enerator was converting a value to a
string for display in an ACCELL/SQL screen field and this string value
overflowed the display format or screen field width.

Correction
120
Modify the display format or screen field to accommodate larger values.

See ACCELL/SQL: Developing an Application for more information
about display formats.
8938
Explanation
Correction
8939
Explanation
Correction
8940
Explanation
Correction
The input string is invalid for the given data type.

ACCELL/M anager could not convert a string to an ACCELL/SQL data
type because the string was invalid for the given type.
Find and correct the invalid string value. See

for more information about valid ACCELL/SQL data type
values.
Not all required fields have been entered ADD REJECTED.
The user tried to add a record to the selected set (and a row to the
database) without entering values for all required fields on the form.
Make sure that all required fields have values before attempting to add
the record.
Mapping of Chook functions failed when opening the database.
ACCELL/M anager could not find all of the database objects in the
database that were referenced in the C-hook functions.
Take these steps:

1. Make sure that you are using the correct database and that the
database design used in your C-hooks marches the current
database design.
2. Make sure that the variables used by your RDBMS to find the
database are set correctly.
If you use this RDBMS:
Then set these variables:
INFORMIX Online
INFORMIX SE
INGRES
ORACLE
SYBASE SQL Server
DSQUERY and SYBASE
Unify DataServer
DBPATH and DBNAME
3. Recompile all the C-hook functions and relink your custom

Manager.
121
See for more information about

writing C-hook functions. For information about setting configuration
variables, see ; for descriptions
of individual configuration variables, see

.
8941
Explanation
Correction
8942
Under normal conditions, a commit or abort of an ACCELL/SQL

transaction should not fail. This error probably indicates a serious
problem in the administration of the current database.
Make sure that the database transaction log is not full, that the journal is
not off-line, and that transaction logging is turned on if you are aborting
a transaction. See your RDBMS manuals for more information about
database administration.
An invalid regular expression was passed to

reg_exp_str_compare$().
Explanation
The reg_exp_str_compare$() form script system function was passed a

regular expression that it could not interpret.
Correction
Find the function call for reg_exp_str_compare$() and check the regular
expression arguments. See
for more information about the reg_exp_str_compare$() form

script system function.
8943
Explanation
Correction
122
A commit or abort of a transaction has failed.
Null values are not supported in the underlying database.

The command was executed in an application whose RDBMS
does not support null values.
Do not attempt to use the SET NULL command unless your RDBMS
supports null values.
8944
ACCELL/SQL cannot run on this size of terminal.
Explanation
The number of rows or columns for your terminal is not in the range of a
screen sizes that are valid for ACCELL/SQL .
Correction
Adjust your termcap and unicap files so that they specify appropriate
row and column screen sizes. If your terminal does not support row and
column values in the ACCELL/SQL valid screen size range, you must
find another terminal.
8945
Explanation
Error initializing ACCELL/SQL environment: os_error.

ACCELL/M anager was initializing its internal data structures and found
an internal error. The status, os_error indicates the error status returned
by the operating system.
Correction
8946
Explanation
Correction
8947
Explanation
Correction
8948
Explanation
Correction

Illegal initial memory size: size.
The AMGR_INI_M_SZ configuration variable was set to an invalid size
value.
Set the AMGR_INI_M_SZ configuration variable to a valid size. This
variable is described in
.
Illegal maximum sort memory size: size.
The AMGR_SRT_M_SZ configuration variable was set to an invalid size
value.
Set the AMGR_SRT_M_SZ configuration variable to a valid size. This
variable is described in
.
Illegal selected set directory name: directory_name.
The AMGR_SEL_SET_DR or AGEN_SEL_SET_DR configuration variable
was set to an invalid directory_name value.
Set the AMGR_SEL_SET_DR or AGEN_SEL_SET_DR configuration
variable to a valid directory search path. These variables are described in

.
123
8950
Explanation
Cant initialize mode messages, see error file.

ACCELL/M anager or ACCELL/ Generator could not initialize its system
variables that describe the current mode.

Correction
8951
Could not read the error message archive (SERRORS).
Explanation
ACCELL/M anager or ACCELL/G enerator could not read the SERRORS

file. This file contains internal error message forms for ACCELL/M anager
and ACCELL/ Generator.
Correction
sure that the SERRORS file exists in the directory specified by the UNIFY
configuration variable and that the current user has read permission on it.
If these fixes fail, you may need to restore the SERRORS file from a
backup.
8952
Explanation
Correction
8953
Explanation
Correction
124
Make sure that the UNIFY and AMGR_ERFL (for the Manager) or
AGEN_ERFL (for the Generator) configuration variables are set so that
they specify the correct directory and file names. After you set
AMGR_ERFL or AGEN_ERFL to an error file name, execute the program
again. Then examine the diagnostic information in the error file to
determine whether ACCELL/SQL ran out of memory or the error message
file has a problem.
Illegal number of open archives archive_number.

The configuration variable OPNARCHS was set to an invalid
archive_number value.
Make sure that the OPNARCHS configuration variable is set to a valid
archive number. This variable is described in

.
Command line access level must be between lower_limit and
upper_limit.
ACCELL/M anager found an invalid value for the application access code.
The access code, which is the last argument on the AMGR command
line, determines which of the four interactive database operations the
user can perform during application execution.
See

for
more information about this AMGR command line argument.
8954
CLEAR_FIND_EXP attributes type does not match target fields
type.
Explanation
Correction
8955
Explanation
Correction
8956
An attempt was made to assign a Clear to Find expression to a target

fields CLEAR_FIND_EXP attribute, but the data type of one of the
expressions values was incompatible with the target fields data type.
Find the form script statement that sets the CLEAR_FIND_EXP attribute
and make sure that the Clear to Find expression evaluates to a value that
has the same data type as the target field. See

for more information about setting Clear to Find
expressions.
The specified help form could not be found in the specified help
archive.
While executing a DISPLAY HELP statement, the Manager could not
find the specified help form in the specified help archive file.
Locate the problem DISPLAY HELP statement and make sure that the
specified or default help form name exists in the specified or default help
archive. Help archives can be examined with PAINTHLP or H2ASC.
Also, make sure that the archive is located in the correct directory and
that the current user has read permission for the file.
Record number is outside of the current selected set.
Explanation
A NEXT ACTION IS RECORD record_number or CHANGE CURRENT

RECORD record_number statement was executed with an invalid
record_number expression.
Correction
Locate the problem statement and change the form script so that it cannot
specify a record number outside of all possible selected sets. The
current_record_count$() and current_record_num$() system
functions can be used to determine the size of the selected set and the
current position in the selected set.
8957
Explanation
Invalid value for this statement.

This error occurs when ACCELL/M anager is executing a statement and
encounters an invalid value for a particular parameter of the statement.
For example, the NEXT ACTION IS RECORD record_number statement
requires that record_number be a defined, non-null NUMERIC value.
125
Correction
8958
Explanation
Locate the problem statement and make sure all possible values in
question are defined, non-null, and of the correct type.
Could not get database information.
ACCELL/M anager could not access its own information about the current
RDBMS product to be interfaced with. This error should not normally
occur.
Correction
8959
Explanation
Correction
8960
Invalid Username/Password.
An ACCELL/SQL executable such as ACCELL/M anager or
ACCELL/G enerator cannot log in to the database by using the current
user name and password. The user name and password can be specified
on the command line, by the DBUSER configuration variable, or
interactively on the database login form.
Make sure that the user name and password is valid for the current
database and that they are specified by using the correct uppercase or
lowercase characters. Also, make sure that the DBTYPE configuration
variable matches the current database type (is set to U2000, ORACLE,
SYBASE, etc.). Another possible problem is that the database may not be
accessible or set up correctly.
Invalid number of zoom values returned.
Explanation
The number of zoom values returned from a zoom form does not match
the number of variables in the INTO clause of the ENABLE ZOOM
statement on the calling form.
Correction
Make sure that a ZOOM RETURN VALUES statement with the same
number of values as the INTO clause of the ENABLE ZOOM statement
is in effect on the zoom form when the
command is
executed. It is also important that the data types of the values brought
back from the zoom form match those expected by the calling form.
8961
Explanation
126
Make sure that the DBTYPE configuration variable is set correctly. If

The record has changed since the last read.

On some RDBMS products, the current record is not locked in record
consistency. In this case, when a record is updated, it may already have
been updated by another user.
This error occurred because ACCELL/M anager discovered that the record
it was trying to update had already been updated by another user. The
attempted operation is not allowed, and the current record is refreshed
with the current data from the database.
The message can also be displayed when only one user is on the system.
In such a case, a row is accessed by one transaction on a form, then you
move to another form on which you update the row that was read by the
previous forms transaction. After updating the row, you return to the
previous form. The two transactions are treated as users by
ACCELL/M anager.
Correction
Try the operation again if you are working on a system with other users.
To guarantee that the message does not display when two forms
(transactions) are accessing the same row, add the following statement to
the ON FORM RETURN section of the form script for the first form:
NEXT ACTION IS RECORD current_record_num$()
Adding this statement causes the current row to be reread so that any
operations performed on it do not generate error 8961.
8962
Explanation
The record you are attempting to update or delete has been deleted.
On some RDBMS products, the current record is not locked in record
consistency. In this case, when a record is updated or deleted, it may
already have been updated or deleted by another user.
This error occurs because ACCELL/M anager discovered that the record it
was attempting to update or delete had already been deleted by another
user. The attempted operation is not allowed, and the current record is
removed from the selected set.
Correction
8963
Explanation
If you need this record to be in the database, you can insert it by

executing the
and
commands.
The record you are attempting to position on has been deleted.

In record consistency, records other than the current row are not locked.
This means that another user can delete any record other than the current
record.
127
This error occurs when you are trying to position on a record that has
been deleted. Because ACCELL/M anager cannot position on a record that
does not exist, it will position on a neighboring record.
Correction
8965
Explanation
Correction
8966
Unable to validate licensing information.

At installation time, licensing information is installed into certain
executables. This error indicates that the licensing password has not been
installed correctly, the expiration date has been exceeded, or the software
is not licensed to run in the current configuration, such as on the current
host or on the current date.
Contact Unify Customer Support to get a valid licensing password and
install it on the required executables.
The data type in the C-hook return value is invalid.
Explanation
The C-hook return value includes the data type, the value, the define
flag, and the null flag. The data type specified is not an ACCELL/SQL
data type (A_INT, A_FLT, A_BOOL , A_STR, A_DATE, A_TIME,
A_AMNT, A_TXTM, A_TXTF, A_BINM, or A_BINF), and the value is a
null value.
Correction
Review the C-hook function source code to verify that the return value is
specified correctly. The procedure for returning values from C-hook
functions is described in
.
8967
Explanation
Correction
128
This message is informational in nature and requires no correction.
An X Window toolkit error occurred.

An internal X toolkit error occurred while running ACCELL/M anager.
8970
Explanation
Correction
8971
Invalid setting of ACLPRESMODE configuration variable.

ACCELL/M anager could not be started because of an invalid setting of
the ACLPRESMODE configuration variable. Valid settings are
CHARACTER, MOTIF, and OPENLOOK , based on the presentation
layer (user interface). The default is CHARACTER.
Make sure that the configuration variable either is set to one of the three
valid values or is not set (to use the default character mode). For more
information about the ACLPRESMODE configuration variable, see

.
Illegal command action specifier string.
Explanation
ACCELL/M anager found an invalid command action specifier string

while executing the DEFINE COMMAND section or a SET COMMAND
statement. The valid command action specifier strings are ENABLED or
DISABLED. The default, if not specified, is ENABLED.
Correction
Find and correct the appropriate DEFINE COMMAND section a SET

COMMAND statement. For the syntax and usage of the DEFINE
COMMAND section, see

.
8972
Explanation
Illegal label action specifier string.

ACCELL/M anager found an invalid label action specifier string. A valid,
defined, non-null string expression is required. The label action specifier

string can appear
after the LABEL IS, AUD_LABEL IS, or FIND_LABEL IS
keywords in a DEFINE COMMAND section
after the LABEL TO, AUD_LABEL TO, or FIND_LABEL TO
keywords in a SET COMMAND statement
Correction
Find and correct the appropriate ACCELL/4GL statement. For the syntax
and usage of the DEFINE COMMAND section and SET COMMAND
statement, see

.
129
8973
Explanation
An illegal key string was assigned to a commands key attribute.

ACCELL/M anager found an invalid key string after the KEY IS or KEYS
ARE keywords while executing DEFINE COMMAND section or after the
KEY[S] TO keywords in the SET COMMAND statement. A valid,
defined, non-null string expression is required.

Correction
8974
Explanation
Find and correct the appropriate DEFINE COMMAND section or SET

COMMAND statement. For the syntax and usage of the DEFINE
COMMAND section and SET COMMAND statement, see

.
An illegal function key number was encountered.

ACCELL/M anager found an invalid function key reference while
executing the DEFINE COMMAND section or SET COMMAND
statement. The function key reference must be of the form

NONE<Key>Fnn, where nn is one or two digits that identify a function
key (for example, F4 or F10).
Correction
Determine the allowable function keys for your system. Find and correct
the appropriate DEFINE COMMAND section or SET COMMAND
statement.
For the syntax and usage of the DEFINE COMMAND section and SET
COMMAND statement, see

. See your operating system programmers manual for
information about allowable function keys.
8975
Explanation
Correction
130
Busymouse file read error.

ACCELL/M anager found an error while trying to read the busymouse
bitmap file. The specified path for the busymouse file must be relative to
the current directory or relative to the UNIFY configuration variable.
Verify the spelling of the file if mentioned on the command line.

Otherwise check the value specified in the resource file, and make sure
the file exists and the file permissions allow read access to the current
user.
8976
Explanation
Bad form location coordinates.

ACCELL/M anager found bad form coordinates for the maximum rows
and columns in resource file. A form has been activated whose

position/size exceeds those maxima.
Correction
8977
Explanation
Correction
8979
Explanation
Correction
Change the maximum rows and columns values in your resource file or
change the size or position of the form by using ACCELL/G enerator.
A bad timer id(s) was encountered in the delete timer statement.

ACCELL/M anager found one or more bad timer ID values while
executing the DELETE TIMER EVENT statement.
Check the timer ID values for valid values. Valid values are the ones
assigned to the timer reference variables when the timer is created. See

of the DELETE TIMER EVENT statement.
Illegal timer function argument.

ACCELL/M anager found an illegal value for one of the arguments to a
timer event statement. For the CREATE TIMER EVENT statement, a
valid defined floating point value or expression must be used for the time
specification. For the DELETE TIMER EVENT statement, the event ID
must be a defined numeric value.
Find and correct the seconds argument in the appropriate CREATE

TIMER EVENT or DELETE TIMER EVENT statement. See

of the CREATE TIMER EVENT and DELETE TIMER EVENT
statements.
8980
Explanation
Timer event creation failed.

Timers may be a limited resource on your system, depending on the user
interface option that you are using. The error can occur in these cases:
ACCELL/M anager finds an X Window toolkit error during the
timer event creation when you use the Motif or OPEN LOOK UI
option.
131
You have exceeded the maximum number of timers allowed by the

version of Microsoft Windows that you are using. On Windows,
the maximum number of timers is a resource that is shared by all
applications, not used only by ACCELL/SQL .
ACCELL/M anager runs out of memory in either a GUI mode or
character mode. This is an internal ACCELL/M anager error.
Correction
If this error occurs, try reducing the amount of memory used by the
application. On Windows, if you have too many timers active, try closing
other Windows applications or try reducing the number of timers used by
the ACCELL/SQL application.
If the error persists, please call Unify Customer Support.
8981
Explanation
Queued command execution failed.

ACCELL/M anager could not execute a Queue command because it is not
valid in the current mode.

Correction
8982
Queued command not enabled in current mode.
Explanation
ACCELL/M anager could not execute the QUEUE COMMAND statement

because it has been disabled for the current presentation mode.
Correction
Check the DEFINE COMMAND section or SET COMMAND statement

for the command action specifier for the current presentation mode. See

of the DEFINE COMMAND section and SET COMMAND statement.
8983
Explanation
Correction
132
Find the appropriate queued command in the ACCELL/4GL script file and
correct the command action appropriately. See

for the syntax and usage of the QUEUE COMMAND
statement.
An invalid button location has been given.

ACCELL/M anager (AMGR) found an invalid location for a user-defined
button. This error occurs if the row and column specified for a button are
outside the form. In such a case the button is not created on the form
(much like it was specified with NOT ON USERMENU), although the
key sequences are still valid.
Make sure that the row and column specified for the button in the
DEFINE COMMAND section are within the boundaries set for the
current form.
ACCELL/SQL Interactive Debugger

Error Messages
-8984
Explanation
Correction
-8985
Explanation
Correction
-8986
Explanation
Correction
-8987
Explanation
Correction
Invalid line number was specified.

You have specified a line number that exceeds the number of lines in the
source file.
Specify a lower number when you execute the command.
Invalid field name was specified.

The specified variable is not associated with the specified form (if one
was specified) or the current form (if no form was specified).
Verify the spelling of the variable and form name (if specified) and make
sure that the variable exists on the specified form. If no form was
specified, either specify it or make the form current by using the form
command.
Invalid arguments specified with this command.

The command arguments you have entered on the command are not
valid.
Reenter the command with the correct arguments. To determine the valid
arguments, see the command descriptions in ACCELL/SQL Interactive
Debugger: Developer's Reference, or execute the help command for that
command to display the complete syntax.
TO keyword missing on the command line.

TO is a required keyword of this command.
Execute the command again with the correct syntax.
ACCELL/SQL Interactive Debugger Error Messages
133
-8988
Explanation
Correction
-8989
Explanation
Correction
-8990
The numeric value entered on the command line is not valid.

Reenter the command with a valid value. See the command descriptions
in ACCELL/SQL Interactive Debugger: Developer's Reference, or
execute the help command for that command to display the complete
syntax.
There is no active form.

This command requires a current form.
Make a form current and then execute the Debugger command again.
Invalid form attribute or field name was specified.
Explanation
This command requires that you specify a valid form attribute or a valid
variable.
Correction
Reenter the command with a valid attribute or variable. See the

commands description in ACCELL/SQL Interactive Debugger:
Developer's Reference, or execute the help command for the command
to display the complete syntax. For information about attributes, see
ACCELL/SQL: Script and Function Reference .
-8991
Explanation
Correction
-8992
Explanation
Correction
134
Invalid value was specified.
Invalid field attribute was specified.

The field attribute that you have specified does not exist or is spelled
incorrectly.
For information about attributes, see ACCELL/SQL: Script and Function
Reference .
Invalid form name was specified.
The application does not include a form with the specified name.
Check the spelling of the form name. Execute the command again with
the correct form name.
-8993
Explanation
Correction
-8994
Invalid break point was specified.

One of the arguments specified with this breakpoint command is not
valid.
Reenter the command with valid arguments. See the command
descriptions in ACCELL/SQL Interactive Debugger: Developer's
Reference, or execute the help command for that command to display the
complete syntax.
Invalid debugger license.
Explanation
The Debugger software must be licensed before you can execute the
debugger.
Correction
Obtain a valid, activated software license that supports the debugger

option and install the license as directed.
-8995
Invalid current line no.
Explanation
Either the line number used with this command does not include any
ACCELL/4GL statement, or the current source file is not associated with
the current form.
Correction
View the source file to obtain a line number that has an executable
statement. Use the form command to make the associated form current.
-8996
Invalid command from a file.
Explanation
One of the Debugger commands specified in the input environment file

is not valid.
Correction
Only the commands used to modify the debugging environment, such as

breakpoint, watchpoint, assign, and alias, are valid in the input file.
-8997
Invalid Presentation Mode specified for the ACCELL/SQL Debugger.
Explanation
This release of the debugger cannot be used with the graphical user
interfaces (GUI mode).
Correction
Set the ACLPRESMODE configuration variable to CHARACTER and

execute the application in character mode if you want to use the
debugger.
135
-8998
Invalid file name was specified.
Explanation
The file specified with the file command is not associated with the
current form. This is not a syntax error; you can view the file as needed,
but you cannot perform execution control operations, such as setting
breakpoints or watchpoints, on the form.
Correction
To set breakpoints or watchpoints on the associated form associated with

the file, you must make the form current (execute the form command) or
specify the complete form and file names in Debugger commands.
-8999
Explanation
Correction
Invalid debugger command was specified.

An invalid debugger command was entered on the command line,
specified as an argument to the help command, or read from an
environment file.
Reenter the command correctly. See the command descriptions in
ACCELL/SQL Interactive Debugger: Developer's Reference, or execute
the help command for a specific command or to display a complete list

of commands.
136
ACCELL/Manager Error Messages

The following messages may be displayed by ACCELL/M anager
(AMGR) while executing an application.
9000
Array subscript out of bounds.
Explanation
An array reference was made with a subscript that was out of bounds in
the ACCELL/4GL form script.
Correction
Fix the form script to check for out of bounds array references by using
the LIST_UPPER_BOUNDS , LIST_LOWER_BOUNDS ,
ROW_UPPER_BOUNDS , ROW_LOWER_BOUNDS ,
COLUMN_UPPER_BOUNDS , COLUMN_LOWER_BOUNDS array
attributes. Also, the array could be changed to a unbounded array by
using the UNKNOWN keyword in the array definition.
9001
Explanation
Correction
9002
Invalid type for array subscript.

An array reference was made with a subscript whose type was not
numeric.
Find the array reference in the application form script and make sure that
the types of all array subscripts are numeric.
Cannot reference an undefined array.
Explanation
During the activation of a form, ACCELL/M anager tries to resolve

references to ambiguous symbols made in the form script. If the symbol
references a scalar (non-array) variable, space is allocated for that
variable, and it is made local to the form being activated. If the symbol
references an array variable, ACCELL/M anager cannot determine how
much space to allocate for that array and generates an error.
Correction
Define the array either in a LOCAL statement or in ACCELL/G enerator.
137
9003
Subscript missing from array reference, value is undefined.
Explanation
An array was referenced without a subscript in the form script.
Correction
9004
Invalid array dimensions.
Explanation
An arrays size can be dynamically defined at runtime by using variables

as array dimensions in the LOCAL statement. If the variable expressions
resolve to undefined values or non-numeric types, or the lower bound is
greater than the upper bound, ACCELL/M anager generates an error and
leaves the array undefined.
Correction
Make sure that the expressions used to define dynamic arrays resolve to
defined numeric values where the lower bounds are less than or equal to
the upper bounds.
9005
There is not enough memory to grow an unbounded array.
Explanation
ACCELL/M anager has run out of memory attempting to grow an

unbounded array. Unbounded arrays are enlarged or grown when they are
referenced by using subscripts that are beyond their originally defined
upper bounds.
Correction
Same as 8804. To avoid fragmentation, when defining unbounded arrays,

make a best guess for the size of the array by using the ESTIMATING
clause. This helps ACCELL/M anager to determine the size of its array
blocks.
9006
Explanation
Correction
138
Find the array reference in the form script, determine which cell of the
array is being referenced ,and add the array subscript.
Clear to add expressions are not supported for unbounded arrays.

An attempt was made in the form script to set an unbounded arrays
CLEAR_ADD_EXP attribute. Unbounded arrays cannot use the
CLEAR_ADD_EXP attribute.
Make sure that you do not use the CLEAR_ADD_EXP attribute with an
unbounded array. Change such an array to a bounded array or initialize
the unbounded array by using a FOR loop in the ON CLEAR TO ADD
event section.
9007
The parameter types for an ACCELL/SQL function call do not

match.
Explanation
The types of the parameters being passed to a global ACCELL/SQL

function call do not match the types in the function definition. This
means that the function declaration where the function is called from is
different from the function definition where the code for the function
exists.
Correction
Make sure that the function declaration and the function definition have
matching parameter types.
9008
Explanation
Correction
9009
Invalid attribute, a scalar cannot reference an array attribute.

An attempt was made to reference an array attribute with a scalar
(non-array) variable.
Make sure that the array being referenced is defined. Arrays can be
defined either in ACCELL/G enerator or in the form script.
Invalid attribute, a list array cannot reference a matrix attribute.
Explanation
An attempt was made to reference an array matrix attribute with an array

list variable.
Correction
Make sure that the correct array is being referenced. If the correct array is
being referenced, make sure that it has been defined with the correct
number of dimensions. A list array has one dimension, and a matrix
array has two dimensions.
9010
Invalid attribute, a matrix array cannot reference a list attribute.
Explanation
An attempt was made to reference an array list attribute with an array

matrix variable.
Correction
Make sure that the correct array is being referenced. If the correct array is
being referenced, make sure that it has been defined with the correct
number of dimensions. A list array has one dimension, and a matrix
array has two dimensions.
139
9011
Explanation
Correction
9012
Explanation
Correction
9013
Explanation
Correction
9014
Explanation
Correction
9015
Explanation
140
Invalid array subscript.

An invalid subscript was used while referencing an array in the
ACCELL/SQL interactive debugger.
Make sure that numeric values are being used for array subscripts.
Invalid array subscript, missing right bracket.

The right bracket ( ] ) is missing from an array cell reference in a
debugger statement.
Make sure that every array cell reference is closed with a right bracket
( ] ) when using the debugger.
Illegal form cache size: size.

The AMGR_FORM_CA_SZ configuration variable was set to an invalid
value of size.
Make sure that the AMGR_FORM_CA_SZ configuration variable is set to a
valid size. This configuration variable is described in

.
Illegal global function cache size: size.
The AMGR_FUNC_CA_SZ configuration variable was set to an invalid
value of size.
Make sure that the AMGR_FUNC_CA_SZ configuration variable is set to a
valid size. This configuration variable is described in

.
An invalid stack address was encountered.
This error may occur when an ACCELL/SQL application is running with
form or function caching turned on. It indicates that ACCELL/M anager
encountered an error in managing the stack memory area. This is an
internal error and should not occur in the normal execution of an
Correction
9016
Explanation
If this error occurs, please call Unify Customer Support. Meanwhile, try
running the application with form or function caching turned off. See
form and function caching. See

for information about the AMGR_FUNC_CA_SZ and
AMGR_FORM_CA_SZ configuration variables.
The referenced identifier does not refer to a form.

The form being referenced is actually a global function, not a form, and
the operation being requested can be performed only on a form.
Statements that operate only on forms (not functions) include these:
the ENABLE ZOOM statement
the DISPLAY TRIM statement
assignment/retrieval of form attributes
Correction
9017
Explanation
Correction
9018
Explanation
Determine which statement references a function where a form is

required and rewrite the statement. See

for the syntax and usage for these ACCELL/4GL
statements.
The current form is read only, insert/update/delete not allowed.

An insert, update, or delete operation can not be done on the current form
because the form is read only (for example, the target table may be a
nonupdateable view). Only reads of the underlying target table are
allowed.
Verify that update operations are not allowed on the forms target table.
Do not attempt to update the form.
Operation not allowed.

An attempt to perform an interactive INSERT, UPDATE, DELETE,
CLEAR TO ADD, CLEAR TO FIND, or FIND command was denied.
141
Correction
Try these solutions:

Verify the settings of the forms form attributes that control which
interactive database operations are permitted for the form
(ADD_ALLOWED, DELETE_ALLOWED , FIND_ALLOWED ,
UPDATE_ALLOWED ).
Also verify the settings of the system variables that control the
users application access privileges for the various interactive
database operations for all standard application forms
(add_allowed$( ), delete_allowed$( ), find_allowed$( ), and
update_allowed$( )).
9019
Explanation
The ACLVARMEMLIM configuration variable was set to an invalid value

of length.
Correction
Make sure that the ACLVARMEMLIM configuration variable is set to a

valid value. This configuration variable is described in

.
9020
Illegal variable length data file directory name:

directory_search_path.
Explanation
The ACLVARDIR configuration variable was set to an invalid value of

directory_search_path.
Correction
Make sure that the ACLVARDIR configuration variable is set to a valid

directory search path and that the specified directory exists. The
ACLVARDIR configuration variable is described in

.
9021
Illegal maximum number of open variable length data files: number.
Explanation
The ACLMXOPNVARF configuration variable was set to an invalid value

of number.
Correction
142
Illegal variable length data inmemory limit: length.
Make sure that the ACLMXOPNVARF configuration variable is set to a

valid number of files. The ACLMXOPNVARF configuration variable is
described in

.
9024
Explanation
Correction
There was an error while reading/accessing a variable length data

file.
ACCELL/SQL stores TEXT and BINARY values whose length exceeds
the value of the ACLVARMEMLIM configuration variable in temporary
files. Also, the user may read TEXT and BINARY values from user files
by using the RETRIEVE statement. An attempt to read or access one of
these files failed.

Make sure that the directory specified by the ACLVARDIR
configuration variable exists and that the permissions allow read
access to the current user.
If the offending ACCELL/4GL statement is a RETRIEVE
statement, make sure that the specified file exists and that the
permissions allow read access.
If the application contains Chooks that adjust the length stored in
the AVAL structure for TEXT or BINARY values, make sure that
the lengths are set correctly.
ACLVARMEMLIM and ACLVARDIR are described in

.
9025
Explanation
Correction
There was an error while writing to a variable length data file.

ACCELL/SQL stores TEXT and BINARY values whose length exceeds
the value of the ACLVARMEMLIM configuration variable in temporary
files. Also, the user may store TEXT and BINARY values to user files by
using the STORE statement. An attempt to write to one of these files
failed.

configuration variable exists and has the correct write permissions.
If the offending ACCELL/4GL statement is a STORE statement,
make sure that the user has write access for the file to be written
to. Also make sure that you have not run out of disk space.
ACLVARMEMLIM and ACLVARDIR are described in

.
143
9026
A file that was to be created already exists.
Explanation
The CREATE file mode open option was to be used by a STORE

statement for the output TEXT or BINARY file, but the file to be created
already exists.
Correction
Find the offending STORE statement and rewrite it with a different file
open mode option, or remove the file before the STORE statement tries
to recreate it. For the syntax and usage for the STORE statement, see

.
9027
Explanation
An expression or variable must be of type TEXT or BINARY.

An expression or variable was used in an ACCELL/4GL context that
requires a TEXT or BINARY value, but the expression or variable is not
TEXT or BINARY.
For the STORE statement, the expression to be stored must result
in a defined value of type TEXT or BINARY.
For the RETRIEVE statement, the variable into which the value is
to be retrieved must be of type TEXT or BINARY (as specified in
the RETRIEVE statement), or be a general variable whose type has
not yet been set.
Correction
9028
Invalid value was specified for WINDOW_HEIGHT field attribute.
Explanation
The screen field attribute WINDOW_HEIGHT was set to an invalid

value. Only screen fields of type TEXT may have a value greater than
one for WINDOW_HEIGHT.
Correction
144
Find the offending STORE or RETRIEVE statement and rewrite it. For
the syntax and usage of the STORE and RETRIEVE statements, see

.
Find and rewrite the ACCELL/4GL statement that is setting

WINDOW_HEIGHT to an invalid value. For more information about the
WINDOW_HEIGHT field attribute, see

.
9033
Insufficient heap memory to display text in field.
Explanation
ACCELL/M anager ran out of heap space when trying to display the field.
This is not a fatal error, but a warning that heap memory is getting very
scarce. A fatal error could occur soon if you do not exit AMGR now.
Correction
Exit ACCELL/M anager and increase the size of ACCELL/M anager heap
memory by resetting the AMGR_HPSZ configuration variable to a larger
value. For information about the AMGR_HPSZ configuration variable, see

.
9034
Explanation
Insufficient heap memory to edit text in field. Use system editor.

ACCELL/M anager ran out of heap memory preparing your data for
editing. You may be able to edit the data by using the system editor.
Correction
9035
Explanation
Correction
To prevent a fatal error, exit ACCELL/M anager and increase the size of
ACCELL/M anager heap memory by resetting the AMGR_HPSZ
configuration variable to a larger value. For information about the
AMGR_HPSZ configuration variable, see

Last operation required more heap than available. Last edit lost.
Your last edit operation caused the field editor to request more heap
memory than was available for your application.
Although the last edit may have been lost, you can probably save your
other edits. To save the other edits, update the current record. Then exit
ACCELL/M anager and increase the size of ACCELL/M anager heap

145
9036
Insufficient heap size to edit the current text line. Adjust heap size.
Explanation
ACCELL/M anager ran out of heap memory preparing the current text line
for editing. This can occur if the current text line is very long (for
example, several text lines have been joined) or if ACCELL/M anager has
only a small amount of heap memory available.
Correction
You may be able to edit the entire text variable in the system editor, but
this may be risky if ACCELL/M anager does not have enough heap
memory to save your edits from the editor. However, you may be able to
save your previous edits by updating the current record.
Exit ACCELL/M anager and increase the size of ACCELL/M anager heap

9037
Explanation
The record you are attempting to position on has an undefined row

id.
While trying to change the current record in the selected set,
ACCELL/SQL has encountered a record with an undefined row identifier.
Without a defined row identifier ACCELL/SQL cannot retrieve the row
from the database.
This can occur when a new record has been added to the selected set and
not all values for the row identifier were specified during the insert
operation. The record is automatically deleted from the selected set;
however, the database is not affected.
Correction
First, use the ridutil utility to determine which columns ACCELL/SQL

uses for its row identifier. Based on the columns being used and the
functionality desired, use one of the following methods to correct the
problem:
If the columns currently being used by ACCELL/SQL for the tables
rowid are inappropriate, use the ridutil utility to change which
columns are used.
Modify the form to make all columns which are part of the row
identifier required.
Add statements to the forms script to set default values for all
columns that are part of the row identifier.
Define clear-to-add expressions for all columns that are part of the
row identifier.
146
9038
Explanation
A record you are attempting to read has an undefined row id.

This error is identical to error 9037, except that multiple records are
affected.
Correction
See the corrective actions recommended for error 9037.
9039
A record you are attempting to read has been deleted.
Explanation
Another user has deleted records that were previously part of your
selected set. These records will automatically be deleted from your select
set. This message occurs only when a form is running in record
consistency mode.
Correction
To prevent records from being deleted by other users use set consistency
when starting the current form. If you simply want a snapshot of the
current records in the database, use the NO CONSISTENCY mode.
9040
Invalid value for $info_level. Setting $info_level to 1 (intermediate).
Explanation
The $info_level system variable has been set to an invalid value and has
been reset to 1. An $info_level of 1 indicates that ACCELL/SQL will
display an intermediate level of error information when an error occurs.
Correction
Make sure that your application sets the $info_level system variable to 0,
1, or 2. Any other value is invalid.
9041
Explanation
Correction
9042
Explanation
Correction
Invalid value specified for a screen fields COL attribute.

An attempt was made to set a fields COL attribute to a value that is
greater than the current forms width.
When setting a fields COL attribute, make sure that it is less than the
current forms width.
Invalid value specified for a screen fields ROW attribute.
An attempt was made to set a fields ROW attribute to a value that is
greater than the current forms height.
When setting a fields ROW attribute, make sure that it is less than the
current forms height.
147
9046
The data type being returned does not match the function definition.
Explanation
The data type of the value returned by a function does not match or is not
compatible with the return data type defined for the function.
Correction
9047
Explanation
Either change the return data type defined for the function in the
FUNCTION statement to match the type being returned or change the
statements that make up the function body so that a value of the proper
type is returned.
A variables CLEAR_ADD_EXP was set on an invalid form.

A variables CLEAR_ADD_EXP is set on a form that is activated after
the form that created the associated target variable. As a result, when this
clear to add expression is evaluated, ACCELL/M anager executes code in
a region of memory that has been freed. (This can corrupt memory and
cause core dumps.)
If this error is received, ACCELL/M anager does not execute the clear to
add expression, but exits instead.
Correction
9048
Explanation
Correction
148
Make sure that you set the CLEAR_ADD_EXP attribute on the same
form that created the target variable.
A Row ID is required for the current operation.

An attempt was made to perform an interactive insert, update, or delete
operation on the forms target table when the target table has nothing that
can be used as a row ID.
Before an interactive operation can be allowed on this target table, you
must add a row ID. The row ID must uniquely identify each row in the
table. See Providing ACCELL/SQL With Row Identification
Information, in ACCELL/SQL: RDBMS Integration.
ACCELL/Generator (AGEN) Error

Messages
9100
Explanation
Correction
9101
The input value is not within the valid field range.

The value entered for the field is outside the value range allowed for this
field. You may have entered a value that is negative, too large, or too
small.
Enter a value that is within the proper range for this field. You can use
the command to find out about the valid values for this
field.
There is no trim to delete.
Explanation
There are no trim characters to delete at the current cursor location. There
may be no existing trim to be deleted.
Correction
Make sure that the cursor is positioned over a character before using the
command. If you are using
or commands, make sure there is enough trim to
delete to the right or the left of the cursor.
9103
There isnt enough room on the form to insert a new line.
Explanation
You cannot enter more lines on this form because the form already
contains trim on each line of the form. This error usually occurs when
you execute the

command when there is form trim below
the line that is being inserted. The trim beneath this line may be causing
the form to be full.
Correction
To insert a new line, you must resize the form. You can also redesign the
form trim so that a new line is not needed. Because form borders are also
trim, you may need to delete the form border before you can add new
lines of trim.
ACCELL/Generator (AGEN) Error Messages
149
9104
Explanation
You cannot enter more characters on this line because the line already
contains a character in each column position. There is a character on the
line up to the last column position.
Correction
If the line is full, try editing in Replace edit mode instead of Insert edit
mode. Use the command to change edit modes.
Because form borders are trim, you may need to delete the form border.
See
creating trim.
9105
Cursor is at left edge of form. You cannot move any farther left.
Explanation
You have tried to move the cursor to the left when the cursor is currently
on the left margin.
Correction
You must have trim to the left of the cursor to be able to move to the left.
See
adding trim.
9106
Explanation
Correction
9109
150
No more characters can be inserted. The current line is full.
Cursor is at right edge of form. You cannot move any farther right.
You have tried to move the cursor to the right when the cursor is
currently on the right margin.
You must have trim to the right of the cursor to be able to move to the
right. See
about adding trim.
Form is at left edge of window. It cannot be moved left any more.
Explanation
You have tried to move the form beyond the left edge of the screen with
the

command. You can move the form only within the
boundaries of the screen.
Correction
Do not attempt to move the form beyond the boundaries of the screen.
See
moving a form.
9110
Form is at right edge of window. It cannot be moved right any more.
Explanation
You have tried to move the form beyond the right edge of the screen with
the

Correction
9111
moving a form.
Form is at top edge of window. It cannot be moved up any more.
Explanation
You have tried to move the form beyond the top edge of the screen with
the

Correction
moving a form.
9112
Form is at bottom edge of window. It cannot be moved down any

more.
Explanation
You have tried to move the form beyond the bottom edge of the screen
with the

command. You can move the form only within
the boundaries of the screen.
Correction
moving a form.
9113
Unreplace commands can only be used while in replace mode.
Explanation
You have tried to replace a character with while the
form is in Insert edit mode. The command is valid
only in Replace edit mode.
Correction
Use the command to change to Replace edit mode.

See
editing in ACCELL/SQL .
151
9114
The cursor cannot move left any more.
Explanation
You have tried to move the cursor to the left when the cursor is currently
on the left margin or when moving the cursor to complete the requested
command would place the cursor to the left of the left margin.
Correction
You must have enough trim to the left of the cursor to be able to move to
the left. See
about adding trim.
9115
The cursor cannot move right any more.
Explanation
You have tried to move the cursor to the right when the cursor is
currently on the right margin or when moving the cursor to complete the
requested command would place the cursor to the right of the right
margin.
Correction
You must have enough trim to the right of the cursor to be able to move
to the right. See
for more
information about adding trim.
9116
Explanation
Correction
The cursor cannot move up any more.

You have tried to move the cursor up when the cursor is currently on the
top margin.
You must have trim above the cursor to be able to move up. See

adding trim.
9117
Explanation
Correction
The cursor cannot move down any more.

You have tried to move the cursor down when the cursor is currently on
the bottom margin.
You must have trim below the cursor to be able to move down. See

adding trim.
152
9118
Explanation
A field does not exist at the current position.

You have tried to perform a field operation such as
,
, , , or on
an area of the form where no field has been defined.
Correction
9119
Explanation
Correction
Move the cursor to an area of the form where a field is defined or define
the field at the current location before performing the field operation. See

creating fields.
An invalid character has been entered.
You have entered an unrecognized command or an invalid character.
Verify that the command sequence that you entered is a valid
Generator command. All valid Generator commands are listed in

.
Make sure that you are inserting valid characters on the form.
If you are performing a command such as , make
sure that you complete the command before entering a new
command or trim.
9120
Explanation
Correction
9121
Explanation
Correction
An invalid character has been entered as a graphics character.

You have tried to insert non-graphics characters on the form when the
form is in Graphics mode.
Make sure you are typing only valid graphics characters. You can use the

command to leave Graphics mode. See

for more information about valid
graphics characters.
Unreplace cannot be used while the cursor is on a screen field.
You have tried to use the command when the cursor
is on a field.
Move the cursor off the field before issuing . Make
sure the form is in the Replace edit mode when using
.
153
9122
A field cannot be created on top of existing trim.
Explanation
You have tried to use the command when the cursor is on top
of existing trim.
Correction
Move the cursor off the existing trim before using . You may
need to move existing trim to define the field at the current location. See

creating fields.
9123
Explanation
Correction
9125
Explanation
Correction
9126
Explanation
Correction
Trim cannot be placed on top of an existing field.

You have tried to define trim on top of a field.
Move the cursor off the field before trying to add trim. You may need to
move the field to add the trim at the current location. See

for more information about creating form trim.
Cannot move farther left. The form is at the leftmost window edge.
You have tried to size the form beyond the left edge of the screen by
using the
or
command. You can size the form
only within the boundaries of the screen.
Do not try to size the form beyond the boundaries of the screen. See

for more information about sizing
a form.
Cannot move farther right. The form is at the rightmost window

edge.
You have tried to size the form beyond the right edge of the screen by
using the
or
command. You can size the form

a form.
154
9127
Cannot move farther up. The form is at the topmost window edge.
Explanation
You have tried to size the form beyond the top edge of the screen by
using the or command. You can size the form
Correction
9128

a form.
Cannot move farther down. The form is at the bottommost window
edge.
Explanation
You have tried to use the or command to size the
form beyond the bottom edge of the screen. You can size the form only
within the boundaries of the screen.
Correction

a form.
9129
Forms left border cannot be moved left any more due to existing
trim.
Explanation
You have tried to use the or command to

decrease the width of the form, but existing trim prevents the form from
going any smaller. You cannot make a form smaller than its existing trim.
Correction
If you must size the form smaller, you must first remove the trim.
Because the form border is trim, you may also need to delete the border.
See
for more information on
sizing a form.
9130
Forms bottom border cannot be moved up any more due to existing

trim.
Explanation
You have tried to use the command to decrease the height of
the form, but existing trim prevents the form from going any smaller.
You cannot make a form smaller than its existing trim.
Correction
If you must size the form smaller, you must first remove the trim.
Because the form border is trim, you may also need to delete the border.
See
for more information on
sizing a form.
155
9132
Explanation
Correction
9133
You have tried to insert trim on top of a field.

Move the cursor off the field before trying to add trim. You may need to
move the field to add the trim at the current location. See

for more information about creating form trim.
Use the DELETE FIELD command to remove a screen field.
Explanation
You have tried to delete a trim character by using

or , but the cursor is on a field.
Correction
Move the cursor off the field before trying to delete trim. To delete a
field, use the command while the cursor is on the field to
be deleted. See
for more
information about deleting fields.
9134
DELETE cannot be used in the middle of a field.
Explanation
You have tried to use a command that deletes trim, but the cursor is
positioned on a field.
Correction
Move the cursor off the field before trying to delete trim. See

deleting fields or trim.
9135
Field cannot be moved here because it will overlap an existing field.
Explanation
You have tried to use

to move a field to a location that is
occupied by a field.
Correction
Move the field to a location where no field exists. See

for more information about moving fields.
9136
156
Trim cannot be inserted while on a screen field.
The field cannot be moved here because it will overlap existing trim.
Explanation
You have tried to use

to move a field to a location that is
occupied by form trim.
Correction
Move the field to a location that contains no trim. See

for more information about moving fields.
9137
Explanation
Correction
9138
Explanation
Correction
9139
Explanation
The command just entered is not recognized.

You have entered an unrecognized command or an invalid character.
Verify that the command sequence that you have entered is a valid
ACCELL/G enerator command. All valid Generator commands are listed
in
. Make sure that you are
inserting valid characters on the form.
An error occurred while trying to delete the form file.

ACCELL/G enerator could not delete the existing form file (.aq or .fq
file). When you save an editing session in ACCELL/G enerator, the
Generator first writes out your edited version of the form to a temporary
file, then deletes the existing form file (.aq or .fq file). As the last step,
ACCELL/G enerator moves the temporary form file to the .aq or .fq file.
Make sure that the current directory has write permission.
An error occurred while trying to write the backup form file.

ACCELL/G enerator could not write the backup version (the .bk file) of
the form file (.aq or .fq file). When you edit a form in the Generator, the
Generator first creates a backup version of your existing form file.
Correction
9140
Explanation
Make sure that the current directory has write permission and that the file
system has enough space to hold the file.
An error occurred while trying to write the temporary form file.

ACCELL/G enerator could not write the current edited version of the form
to a temporary file. When you save an editing session in the Generator,

the Generator first writes your edited version of the form to a temporary
file, then deletes the existing form file. As the last step, the Generator
moves the temporary form file to the .aq or .fq file.
Correction
157
9141
Explanation
Correction
9143
Explanation
An error occurred while trying to write a help file.

ACCELL/G enerator could not write a help file to a help archive.
system has enough space to hold the file. If the help archive has become
corrupt, you may need to recreate it or recover it from a backup.
An error occurred while linking a temporary file to the current file.

ACCELL/G enerator could not move the temporary form file to the .aq or
.fq file. When you save an editing session in the Generator, the Generator
first writes your edited version of the form to a temporary file, then
deletes the existing form file. As the last step, the Generator moves the
temporary form file to the .aq or .fq file.
Correction
9145
An invalid value has been entered.
Explanation
You have typed a command that is not valid while sizing a form. Only a
cursor movement or the , , or
command is valid after you press the , , or
command.
Correction
Make sure that you finish sizing the form before using other Generator
commands. See
for more
information about sizing forms.
9146
158
A field on this form requires input before the form can be updated.
Explanation
You have tried to execute an

on a form than contains
required fields that have not yet had values entered to them. A required
field is a field for which the REQUIRED screen attribute is set to TRUE.
Required fields must have values entered.
Correction
Make sure that all required fields on the form have values before you
save the form information with
. For example, on the Field
Definition form, the Field Name and the Data Type fields are required
fields and must have values.
9147
Explanation
Correction
9148
Explanation
The only valid entries for this field are Yes or No.
You have tried to enter a response other than Yes or No in a boolean
field.
You must type a valid response of Yes or No in a boolean field. You can
use the command to find out about the valid field values.
This isnt a valid field data type. Please reenter the data type.
You have tried to enter an invalid field data type in the Data Type field of
the Field Definition form. The valid ACCELL/SQL data type keywords
are AMOUNT, BINARY, BOOLEAN , DATE, FLOAT, NUMERIC,
STRING, TEXT, and TIME.
Each ACCELL/SQL data type can be entered with a single character code,
except for TIME, which requires a 2-character code:
AMOUNT
BINARY
BOOLEAN
Correction
9149
A
B
B
DATE
FLOAT
NUMERIC
D
F
N
STRING
TEXT
TIME
S
T
TI
You must type a valid data type in the Data Type field. You can use the
command to find out about the valid field values. See

for information about defining a
field with the Field Definition form.
Invalid justification type. Please reenter the justify type.
Explanation
You have tried to enter an invalid justification type in the Display Justify
field on the Field Definition form. The valid ACCELL/SQL field
justification types are LEFT, RIGHT, and CENTERED. Each
ACCELL/SQL justification type can be entered with a single character
code (L, R, or C).
Correction
You must type a valid data type in the Display Justify field. You can try
using the command to find out about the valid field values.
See
defining a field with the Field Definition form.
159
9150
Explanation
You have tried to enter a negative or zero value for a field that requires a
non-negative value. For example, this error occurs when you enter a
negative or zero value in the Field Length field of the Field Definition
form. Field lengths must be greater than zero.
Correction
You must type a non-negative, non-zero value in the current field. You
can use the command to find out about the valid field
values. See
defining a field with the Field Definition form.
9151
The specified input length is too long. Please reenter a new value.
Explanation
You have tried to enter a value that is outside the range of values allowed
for the field. For example, this error occurs when you enter a value in the
Field Length field of the Field Definition form that is greater than the
field length allowed for the fields data type.
Correction
You must type a valid value in the current field. You can use the
command to find out about the valid field values. See

9153
Explanation
Correction
160
A fields input length must be greater than zero. Please reenter a

value.
This field name is already used for another field on this form.
You have tried to enter a duplicate name in the Field Name field of the
Field Definition form. Field names must be unique on a form.
Make sure that you choose a unique field name for your field, or make
sure you pick a unique name when you perform a
for target table
field lookup. See
for information
about defining a field with the Field Definition form.
9154
Explanation
This isnt a valid edit mode. Edit modes are Replace or Insert.
You have tried to enter a response other than Replace or Insert in the
Default Edit Mode field on the Session Defaults form.
Correction
You must type a valid response of Replace or Insert in the Default Edit
Mode field. You can use the command to find out about the
valid field values. See
for
information about setting form editor defaults with the Session Defaults
form.
9155
The form must be made larger before additional trim can be added.
Explanation
Correction
9156
Explanation
Correction
9157
Explanation
Correction
You have tried to add trim on a form that is too small to hold the
additional trim.
Try making the form bigger by using the
or

command before adding the additional trim. See

for information about sizing forms.
Only the characters T or (space) can be used on this form.

You have tried to enter a response other than T, t, or a blank space on the
Setting Tabs form. You are entering an invalid value while entering tab
stops.
You must type a valid response of T, t, or a blank on the Setting Tabs
form. See
setting form editor defaults with the Session Defaults form.
The requested command is inactive in current mode.

You have entered an unrecognized command, an inactive command, or
an invalid character.
Verify that the command sequence you have entered is a valid Generator
command and is active in the current presentation mode (Motif, OPEN
LOOK, or character). All valid Generator commands are listed in

. Make sure that you are inserting
valid characters on the form.
161
9158
Fixed trim cannot be marked within nonrepeating trim.
Explanation
This error occurs when you try to use the

command
on an area of the form that is not a repeating area.
Correction
You can create fixed trim only within a forms repeating area. For
information about creating repeating areas, see

.
9160
The specified database table name cannot be found in the database.
Explanation
This error occurs in these cases:

You have tried to enter an unknown table name in the Target Table
field on the Form Definition form. The table name entered in the
Target Table field must have been defined in the current database,
owner, schema, or user, depending on the RDBMS on which
You have asked AGEN to create a default screen, and the table
name specified on the command line cannot be found in the
current database, owner, schema, or user, depending on the
RDBMS on which ACCELL/SQL is running.
Correction
9161
Explanation
Correction
162
Make sure that you enter a valid target table name. You can issue the
command from the Target Table field to see a list of all valid
target table names. See
for
information about defining a form with the Form Definition form.
An error has been generated from an RDBMS function.

An error occurred while calling an RDBMS function. This is an internal
error and should not occur during the normal execution of
ACCELL/G enerator.
9162
Explanation
Correction
9163
Explanation
Correction
9166
This isnt a valid order entry. Ordering can be by Row or Column

only.
You have tried to enter a response other than Row or Column in the
Field Order field of the Form Definition form. Field order must be
specified as either Row or Column ordering.
You must type a valid response of Row or Column in the Field Order
field. You can use the command to find out about the valid
field values. See
for information
about defining a form with the Form Definition form.
An invalid scroll bar position has been entered.

The scrollbar can be placed on the left or right side of the form or
omitted from the form.
Enter one of the following choices for the scroll bar position:
LEFT
Place the scrollbar on the left side of the form.
RIGHT
Place the scrollbar on the right side of the form.
NONE
Do not place a scrollbar on the form.
The specified field name cannot be found in the target table.
Explanation
You have tried to enter a non-target field name in one of the Sort
Columns fields of the Form Definition form. Sort columns are valid only
if the form has a target table and the sort columns are target table fields.
Correction
If you want to access the rows in a target table in a specific order, enter
the target table fields in order in the Sort Columns fields on the Form
Definition form. You can see a list of target table fields by executing the
command from the Sort Columns field.

See
specifying sort columns on the Form Definition form.
163
9167
Explanation
Correction
9169
Explanation
Correction
9170
You have tried to perform an operation that is valid only for a form that
has a target table defined. Examples of such operations are trying to enter
sort fields on the Form Definition form or entering the

command when the form does not have a
target table.
To perform one of the previous type of operations, make sure that your
form has a target table. A target table is defined on the Form Definition
form by entering a table name in the Target Table field. See

for information about defining
screen forms.
Transaction levels can only be within the range of 17.
You have tried to enter an invalid transaction level number in the
Transaction Level field of the Choose Next Form form. A transaction
level number must be an integer in the range of 1 through 7.
Make sure that you enter a valid transaction level number in the
Transaction Level field. You can use the command to find
out about the valid field values. See

for information about defining a Next form with the Choose Next
Form form.
Blanks cannot be used in field names. Please reenter a field name.
Explanation
You have tried to enter a field name that contains blanks, but field names
cannot contain blank characters. Valid field names must be specified in
the Field Name field of the Field Definition form, the Array Name field
of the Array Definition form, and the First Field field of the Form
Definition form.
Correction
Make sure that you enter a field name that does not contain blanks. See

9171
Explanation
Correction
164
No target table has been specified for this form.
Blanks cannot be used in file names. Please reenter the file name.
You have tried to enter a file name that contains blanks, but file names
cannot contain blank characters.
Make sure that you enter a file name that does not contain blanks.
9172
Explanation
The database has been changed. Use EXPLAIN ERROR for more
information.
The database has been changed since the form was created. The

command can provide additional information about the
error.
Correction
You must remake the form to be compatible with the database design.
9173
The file name is too long. File names are limited to 14 characters.
Explanation
Correction
9174
You have tried to enter a file name that is longer than 14 characters.
Make sure that file names are 14 characters or less.
An invalid case conversion type has been entered.
Explanation
You have tried to enter an invalid conversion specification in the Case

Conversion field on the Field Definition form. The valid ACCELL/SQL
case conversion types are UPPER, LOWER, and NONE. Each
ACCELL/SQL conversion type can be entered with a single character
code.
Correction
You must type a valid conversion specification in the Case Conversion

field. You can use the
command to find out about the valid
field values. See
for information
about defining a field with the Field Definition form.
9175
Explanation
An error occurred while trying to open a window.

ACCELL/G enerator could not open a window. This is an internal error
and should not occur during the normal execution of the

ACCELL/G enerator.
Correction
165
9176
Explanation
Correction
9177
Explanation
Correction
9200
Explanation
Correction
9201
Explanation
Correction
166
The screen field length is longer than the target field length.
You have tried to enter an invalid input length for a target field. Because
a target field is associated with a column in the target table, the length
specified in the Input Length field must match the column length as
defined in the database. You cannot enter an input length that is longer
than the length of the associated target table column.
For a target field, make sure that you enter a value in the Field Length
field of the Field Definition form that is equal to the length of the
associated target table column. See

for information about defining a field with the Field Definition
form.
Only a start transaction is allowed from an application form.
You have tried to enter an invalid transaction level number for the First
form of the application. First forms are defined on the Choose Next Form
for the master application form. The only transaction level numbers valid
for First forms are those that indicate a transaction level of Start Tx.
When defining First forms, make sure that you enter a transaction level
number that indicates that Start TX will be performed. You can use the
command to find out about the valid transaction level
numbers.
An error occurred while opening the form.
ACCELL/G enerator could not open a form file (.aq or .fq file).
Make sure that you have spelled the form name correctly, and that the
form file exists and has the correct permissions. If the form file exists
with the correct permissions, then the form file has probably been
corrupted. Either restore the file from a backup or recreate it.
An error occurred while reading the form.
ACCELL/G enerator could not read a form file (.aq or .fq file).
Make sure that you have spelled the form name correctly, and that the
form file exists and has the correct permissions. If the form file exists
with the correct permissions, then the form file has probably been
corrupted. Either restore the file from a backup or recreate it.
9202
Explanation
Correction
9206
Explanation
An error occurred while closing the form.

ACCELL/G enerator could not close a form file (.aq or .fq file).
Make sure that you have enough disk space for two copies of the form
file (the existing one and a temporary one) before editing a form.
An error occurred while trying to open a screen field help file.
ACCELL/G enerator could not open the help file for the current field.
Either the help file name is invalid but names an existing file, or the help
archive file has been corrupted.
Correction
9207
Explanation
Correction
9208
Explanation
Correction
9209
Explanation
Correction
Make sure that you have spelled the help form name correctly and that
the file exists with the correct permissions. If the help archive file has
been corrupted, either restore the file from a backup or recreate it.
An error occurred while closing a screen field help file.
ACCELL/G enerator could not close the help file for the current field.
Before you edit a form, make sure that you have enough disk space for
two copies each of the form file and the help file (the existing form and
help files and the temporary form and help files).
An error occurred while reading an existing screen field help file.
ACCELL/G enerator could not read the help file for the current field.
the file has the correct permissions. If the help archive file has been
corrupted, either restore the file from a backup or recreate it.
An error occurred while writing a screen field help file.
ACCELL/G enerator could not write the help file for the current field.
Before you edit a form, make sure that you have enough disk space for
two copies each of the help form file and the form file (the existing help
and form files and the temporary help and form files). Also make sure
that you have write permission in the current directory.
167
9213
Explanation
Not enough memory on the heap to write form.

ACCELL/G enerator does not have enough heap space to store the current
form. ACCELL/G enerator keeps a variety of internal information in an
area called the heap.

Correction
Increase the heap size by changing the AGEN_HPSZ configuration

variable. This variable is described in

.
9216
An error occurred while trying to unlink a screen field help file.
Explanation
ACCELL/Generator could not remove or unlink the help archive file.
Correction
the file exists and has the correct permissions.
9217
Explanation
An error occurred while trying to link a screen field help file.

ACCELL/G enerator could not link the help form file. This should only
happen when a file already exists with the name of the file that
ACCELL/G enerator is trying to link to.
Correction
9218
Explanation
Make sure no temporary help form files appear in the current directory.
Temporary help form files begin with hlpa, followed by a number. Also,
make sure that your disk has enough system resources (inodes).
An error occurred while activating the form.

ACCELL/G enerator could not activate a form. This error normally means
that you have run out of memory.

Correction
168
Check the load activity on your system. If the load activity is high, try
running ACCELL/G enerator later, when the load activity on you system is
lower. If the error persists, please call Unify Customer Support.
9219
Explanation
There was an error initializing the keyboard information.

ACCELL/G enerator could not initialize the keyboard information. This
error normally means that either the unicap file or the unify.msg system
message file has invalid data.
Correction
9220
Explanation
Correction
9221
Explanation
Make sure that your UNICAP and UNIFY configuration variables are set
correctly. Make sure that the file specified by UNICAP exists and that it
has correct information. Make sure that the directory specified by UNIFY
contains the unify.msg and unify.cmf files. These files must have correct
permissions and must not be corrupted. For information about the
UNICAP and UNIFY configuration variables, see

.
There was an error initializing the window manager.

ACCELL/G enerator or PAINTHLP could not initialize the window
manager. This error normally means that you have run out of memory.
running ACCELL/G enerator or PAINTHLP later, when the load activity
on you system is lower.
An error occurred while opening internal form file: Field.frm

ACCELL/G enerator could not open the system archive file, Field.frm.
This archive should be located in the directory specified by the UNIFY
configuration variable.
Correction
9222
Explanation
Make sure the Field.frm file exists in the directory specified by UNIFY
and that you have read and write permissions on it. If this error persists,
this file may be corrupted and you should call Unify Customer Support.
An error occurred while reading internal form file: Field.frm

ACCELL/G enerator could not read the system archive file, Field.frm.
This error indicates that Field.frm is corrupted.

Correction
169
9223
Explanation
An error occurred while closing internal form file: Field.frm

ACCELL/G enerator could not close the system archive file, Field.frm.
This error usually indicates that a problem with system resources, the
operating system, or an internal ACCELL/SQL error has occurred.
Correction
9225
Explanation

An error occurred while trying to open window: window_ ID.
ACCELL/G enerator could not open a window for one of its forms. This
error indicates that there is no more system memory available.

Correction
running ACCELL/G enerator later, when the load activity on your system
is lower.
If the load activity is low, this error may indicate an internal error in
ACCELL/G enerator. In this case, please call Unify Customer Support.
9231
Explanation
frminit: Error from wnopen.

ACCELL/G enerator could not open a new window to begin an edit
session. This error indicates that there is no more system memory

available.
Correction
is lower.
9235
Explanation
Correction
170
ASCEND or DESCEND are the only valid entries for this field.
You have tried to enter a response other than Ascend or Descend in the
Sort Order field of the Field Definition form. Field sort order must be
specified as either ascending or descending. Each ACCELL/SQL sort
specification can be entered with a single character code.
You must enter a valid response of Ascend or Descend in the Field
Order field. You can use the command to find out about the
valid field values.
9237
Explanation
Correction
9238
An error occurred while opening a SGLPNT temporary help file.

ACCELL/G enerator or PAINTHLP could not open a temporary help file.
This temporary help file is used to sort help forms in the same help
archive.
directory. Also verify that the /usr/tmp directory exists and that it
contains enough space for the temporary help files created by
ACCELL/G enerator or PAINTHLP.
An error occurred while reading a SGLPNT temporary help file.
Explanation
ACCELL/G enerator or PAINTHLP could not read a temporary help file.

This temporary help file is used to sort help forms in the same help
archive. It is possible that the temporary file was deleted from /usr/tmp.
Correction
Make sure that the /usr/tmp directory exists and that other users on your
system are not deleting files at random from /usr/tmp.
If this error persists, it may be an indication of an internal error in
ACCELL/G enerator or PAINTHLP. In this case, contact Unify Customer
Support.
9239
An error occurred while writing a SGLPNT temporary help file.
Explanation
ACCELL/G enerator or PAINTHLP could not write to a temporary help

file. This temporary help file is used to sort help forms in the same help
archive.
Correction
Make sure that the /usr/tmp directory exists and that it contains enough
space for the temporary help forms created by ACCELL/G enerator or
PAINTHLP. Also make sure that you have read and write permissions in
/usr/tmp.
9241
Explanation
A Generator temporary help file could not be opened.

ACCELL/G enerator could not open or create one of the temporary files in
which it stores some of its internal data.

Correction
Make sure that you have write permissions in the current directory and
that you are not out of disk space.
171
9242
Explanation
Unable to open the Generators temporary file.

ACCELL/G enerator could not access one of the temporary files in which
it stores some of its internal data.

Correction
9243
Explanation
Correction
The Generator has run out of memory.

ACCELL/G enerator or PAINTHLP could not allocate additional memory.
Take these steps:

1. Increase the value of the AGEN_HPSZ configuration variable.
2. If increasing AGEN_HPSZ does not solve the problem, have your
system administrator reconfigure the memory parameters of your
operating system.
9244
Explanation
Correction
9245
Explanation
Internal error while sizing form.

This error may indicate a shortage of memory and should not occur
during the normal execution of ACCELL/G enerator.
If a shortage of memory is not the problem and the error persists, please
call Unify Customer Support.
Internal error while opening a window.

ACCELL/G enerator could not open a window for its internal use. This
error should not occur during the normal execution of

ACCELL/G enerator.
Correction
is lower.
172
9247
Explanation
Correction
9248
Explanation
Unable to execute the system editor.

ACCELL/G enerator could not execute the system editor.
Make sure that the EDIT configuration variable is set to the name of the
system editor. Verify that the directory that contains the system editor
executable is on the directory search path specified by your PATH
configuration variable. For information about the EDIT and PATH
configuration variables, see
.
Could not close the database.

ACCELL/G enerator could not close the database. This error usually
indicates that a problem with system resources or the operating system or

an internal ACCELL/SQL error has occurred.
Correction
9252
Explanation
Correction
Could not open the database.

ACCELL/G enerator could not open the database.
Make sure that you are in the correct application directory. Also, make
sure that you have correctly set the configuration variables used by your
RDBMS to find the database:
If you are using:
INFORMIX
Online
Then set:
INFORMIX SE
INGRES
ORACLE
SYBASE SQL Server
SYBASE and DSQUERY
Unify DataServer
DBPATH and DBNAME
Make sure that you have access to the database and that you have read
and write permissions on the database files.
173
For Unify DataServer:

If the database has been shut down, you may not be able to open the
database. Make sure that the AUTOSTART and OWNERSTART
configuration variables do not prevent you from opening the database.
See UNIFY 2000: Configuration Variable and Utility Reference for
information about these configuration variables.
9253
Explanation
Could not change to the specified schema or database.

ACCELL/G enerator could not switch to the specified database object.
This database object is a database, owner, schema, or user, depending on

the RDBMS on which ACCELL/SQL is running.
Correction
Make sure that you are using the correct database and that the database
design used in your application matches the current database design.
Also, make sure that the owning database object (database, owner,
schema, or user) specified for the application is correct and that the
current user has permission for running the application.
See your RDBMS manuals for more information about databases, owners,
schemas, and users.
9254
Explanation
The UNIFY configuration variable is not set.

ACCELL/G enerator could not find a setting for the UNIFY configuration
variable.
Correction
9255
Explanation
Make sure that the UNIFY configuration variable is set correctly. This
variable is described in ACCELL/SQL: Configuration Variable and
Utility Reference.
Could not create a master application form.
ACCELL/G enerator spawns a new process to create a default master
application form. The spawned process could not create the default
master application form.
Correction
174
Make sure that the UNIFY configuration variable is set correctly. This
variable is described in ACCELL/SQL: Configuration Variable and
Utility Reference.
9256
Explanation
Correction
9260
Could not remove a file.

ACCELL/G enerator could not remove one of its internal files.
Make sure that you have the correct permissions on the current directory.
WARNING! Target table and field information has been cleared.
Explanation
There was a problem retrieving the target table information for this form.
Exiting now with the command saves the form in its current state.
Continuing clears the database information from your form, and the
information is permanently lost if you save the form.
Correction
The best thing to do is exit and make sure that you are accessing the
correct database (or server on SYBASE SQL Server). Also make sure that
you are specifying the correct database, owner, schema, or user name and
password if required. If you know that the target table is not in the
current database or server and still want to work with the form, continue
with the ACCELL/G enerator session by entering the NEXT FIELD
command.
9261
Explanation

ACCELL/G enerator could not access its own information about the
current database product to be interfaced with. This error should not

normally occur.
Correction
Make sure that the DBTYPE configuration variable is set correctly. (For
information about the DBTYPE configuration variable, see

.) If DBTYPE is set
correctly, please contact Unify Customer Support.
175
9263
Explanation
Correction
9265
Explanation
At least one of the target tables for which the MKAP utility was creating
a default form had too many columns. The MKAP utility calls
ACCELL/G enerator to create the form. ACCELL/G enerator calculates how
many fields can fit on the form, based on the sizes of and number of the
target table columns. If the target table has more columns than the form
has field space for, ACCELL/G enerator creates only as many fields as fit
on the form. The excess columns are omitted from the form.
Either manually create the form for the target table that has too many
fields or create the form with MKAP and manually add the omitted
columns, adjusting them as needed.
This array name is already used for another array on this form.
When defining an array on the array definition form, an attempt was
made to redefine an existing array. An array can be defined only once.
Correction
Use an unique array name when defining new arrays.
9266
Unable to change array class from Matrix to List.
Explanation
Correction
9267
Explanation
Correction
An attempt was made to change the number of dimensions of an array on

the array definition form for an array that has existing cells on the form.
To safely redefine the number of dimensions of an array, you must
remove all of its cells from the form.
Invalid array class. Array classes are Matrix and List.
An invalid number of dimensions was specified for an array on the array
definition form.
Arrays can be defined only with LIST or MATRIX dimensions.
9268
This array cell is already referenced by another field on this form.
Explanation
An attempt was made to add an array cell to the form more than once.
Correction
176
Not all fields can be accommodated in the default form.
Each screen field must have a unique name. This rule also applies to
array cells: they can appear on the form only once.
9269
Cannot delete array with existing screen field references.
Explanation
An attempt was made to delete an array that still has cells on the form.
Correction
Before deleting an array from the array definition form, make sure that
all of its cells have been deleted from the form.
9270
Blanks cannot be used in array names. Please reenter an array

name.
Explanation
An attempt was made to set an array name to a name that contained

blanks.
Correction
9271
Set the array name to a name that does not contain blanks.
This array name is already used for a field on this form.
Explanation
An attempt was made to define an array by using a name that has already
been used for a scalar (non-array) field.
Correction
Use a unique name when defining arrays. Make sure that the name is not
already used as a field name on the form.
9272
Target field names cannot be used for array names.
Explanation
An attempt was made to define an array by using a name that has already
been used by a target field in the target table.
Correction
Use a unique name when defining arrays. Make sure that the name is not
already used as a field name on the form.
9273
Explanation
Operation is invalid in middle of a multi-line text field.

This error can occur for a number of reasons:
You have tried to perform an operation to insert or delete a line,
and the line the cursor is currently on contains non-anchored
TEXT fields (fields whose first line is not the current line).
177
You have tried to insert or delete a character, or center a line, but

the resulting operation would cause trim or a field to be overlaid as
a result of moving a multi-line anchored TEXT field or a as a
result of not moving a non-anchored multi-line TEXT field.
When defining a repeating area, the area must include all lines of
any TEXT fields within the area.
Correction
9274
Explanation
Correction
9275
Explanation
Correction
9276
Explanation
Correction
9277
178
Perform the operation on a row that contains the first line of all TEXT
fields on that line, or temporarily change all affected TEXT fields to a
height of one before performing the operation. If you are defining
repeating trim, include all lines of affected TEXT fields in the repeating
area. For more information about ACCELL/G enerator operations on
TEXT fields, see
.
Invalid screen field name.
An attempt was made to define the forms FIRST FIELD by using an
invalid array name.
Make sure that the array cell you are defining as FIRST FIELD exists on
the form. Also make sure that the array subscripts are in the correct order
(row, column).
The binary data type cannot be used for form screen fields.
This error occurs when you try to add a target field of BINARY data type
to a form. BINARY screen fields are not supported by ACCELL/SQL .
Select a different target field to add to the form.
Blanks cannot be used in form names. Please reenter a form name.
An attempt was made to set the form name to a name that contains
blanks.
Set the form name using a name that does not contain blanks.
Field name from this table already used as a screen field or array.
Explanation
The target table specified contains column names that conflict with
existing field or array names.
Correction
Rename the conflicting fields or arrays before specifying your target

table.
9278
Entire text field must be within, or outside of the repeating area.
Explanation
You have tried to move or size a TEXT field so that it would no longer be
entirely within or entirely outside of the repeating area defined for the
form.
Correction
Use the various repeating area commands to see or to modify the

repeating area. See for more
information about defining and displaying the repeating area defined for
a form.
9279
This field name is already used as a sort field.
Explanation
You have tried to enter a duplicate name in the set of sort columns on the
Form Definition form.
Correction
Make sure that you choose a unique field name for each sort field. See
for more information about how
to define the fields comprising the forms sort order on the Form
Definition form.
9280
The form is too large for the terminal screen.
Explanation
You have tried to bring up a form that is too large to fit in the size of the
current terminal screen.
Correction
If you are unsure of the forms size, check its WIDTH and HEIGHT
values in the ASCII version of the form file. Adjust the terminal size
definition to fit the forms size or use ACCELL/G enerator on the form on
another terminal whose screen is larger. See Customizing the termcap
File in

for information
about adjusting the terminal size definition.
9281
Explanation
Correction
Find count must be greater than or equal to 0.

An attempt was made to set the forms FIND COUNT to a value that was
not greater than or equal to zero.
Set the forms FIND COUNT to a value that is greater than or equal to
zero.
179
ACCELL/SQL Utilities Error

Messages
9300
Explanation
Correction
9301
Explanation
Correction
9302
Explanation
Correction
9303
Explanation
Correction
180
Out of memory.
The utility has run out of memory.
Try executing the program later when the system load is lower. You may
need to see your system administrator about increasing the amount of
main memory on your system.
Error opening file: file_name.

The utility could not open the file_name file.
Make sure that the file name is spelled correctly. Also make sure the file
exists and has the correct permissions. The file may be corrupted, in
which case you should either restore the file from a backup or recreate it.
Error reading file: file_name.

The utility could not read the file_name file.
Make sure that the file has the correct permissions. The file may be
corrupted, in which case you should either restore the file from a backup
or recreate it.
Error writing file: file_name.

The utility could not write to the file_name file.
Make sure that the file has the correct permissions. Also make sure that
you have space left in the file system. Check with your system
administrator to make sure you have not exceeded your user limits.
ACCELL/SQL Utilities Error Messages
9304
Explanation
Correction
9305
Explanation
Correction
Error closing file: file_name.

The utility could not close the file_name file. This error should not occur
unless the internal information about the file has been corrupted.
Error creating file: file_name.

The utility could not create the file_name file.
Make sure that the file name is spelled correctly. Also make sure that
another file with this name does not already exist.
Ask your system administrator to determine whether you have exceeded
your user limits in your file system (inodes).
9307
Warning No target table name given.
Explanation
The utility could not retrieve information from the database about a table
because it has a null name (zero length string). The utility continues, but
assumes there is no target table.
Correction
Make sure any target table names used are valid and exist in the database.
9308
Explanation
Warning Invalid target table name given.

This error occurs in these cases:
The utility could not retrieve information from the database about
a table because the table does not exist. The utility continues, but
assumes there is no target table.
The retrieved table information is inconsistent with the
information in the file that is being worked on.
Correction
Make sure you have given the correct table name. Also make sure you
are working in the correct database object: database, owner, schema, or
user, depending on your RDBMS. You may need to specify the S option
on the command line, or have your system administrator change your
default database, owner, schema, or user to be the correct one.
181
9309
Explanation
Correction
9310
Explanation
Correction
9311
The utility tried to use a column that does not exist in the database for
the specified table.
Make sure that you have specified the correct table. Also make sure that
you have spelled the column name correctly and that it is a column in the
specified table.
Invalid transaction token.

The utility found an invalid transaction token for the form.
Make sure that you are specifying a valid transaction token, such as
CONTINUE TX, START TX, or RESTART TX. For information about
specifying ACCELL/SQL transaction tokens, see

.
Warning Invalid ACCELL/SQL TYPE specified: data_type.
Explanation
The utility found an invalid ACCELL/SQL data type for a screen field.
The valid ACCELL/SQL data types for screen fields are NUMERIC,
FLOAT, BOOL , STRING, DATE, TIME, AMOUNT, and TEXT. BINARY
is not a valid screen field data type.
Correction
Make sure you are using one of the valid ACCELL/SQL data types for the
screen field.
9312
182
Warning, column_name was a column in the target table, but is not

now.
Unexpected EndOfFile encountered.
Explanation
The utility unexpectedly reached the end-of-file. This error can occur if
the file is corrupted or you have specified an invalid, but existing file
name.
Correction
Make sure that you have specified the correct file name, and that the file
is not corrupted.
9313
Unexpected token encountered: token_string.
Explanation
The utility found an unexpected, but recognized, token in the input file.
This can occur if the input file is corrupted or you gave the wrong name
for the input file (but it was an existing file).
Correction
Make sure that you have specified the correct file name. Locate the string
specified as token_string in the input file, and determine why the string
is not valid.
9314
Indeterminate window manager error.
Explanation
The utility could not open, read, or write a window, or the window
manager ran out of memory. Even though it is not interactive, the utility
uses the window manager to manipulate borders on forms. The most
common cause of this error is that you are out of memory.
Correction
Determine the load activity on your system. If the load activity is high,
try running the utility later, when the load activity on your system is
lower. If the load activity is low, this error may indicate an internal error.
In this case, please call Unify Customer Support.
9315
Explanation
Correction
9316
Explanation
Indeterminate error while retrieving target table information.

The utility_name utility could not retrieve target table information from
the database, but the table or column names do exist.
Determine whether you have run out of memory, including shared
memory. Also determine whether the database is corrupted.

ACCELL/SQL could not access its own information about the RDBMS
with which to interface. This error should not normally occur.

Correction
Make sure that the DBTYPE configuration variable is set correctly. If

183
9317
Could not open database continuing without database information.
Explanation
The specified database could not be opened. Execution will continue, but
without access to database information.
Correction
Make sure that your database is running. Verify that the appropriate
database environment variables are set. For example, if you are using the
SYBASE RDBMS, check the DSQUERY variable; if you are using the
Unify DataServer RDBMS, check the DBPATH variable.
9318
Warning, type for column column_name changed in database, type

being changed for target variable.
Explanation
The ACCELL/SQL type defined for a target variable is not compatible

with the data type of the corresponding database column. The ASC2Q
utility will automatically change the ACCELL/SQL type to match that of
the database column.
Correction
Run Q2ASC on the new form file. Then compare the old and new ASCII
files to verify that the changes made are appropriate.
9319
Warning, length for column column_name changed in database,

length being changed for target variable.
Explanation
The database field length defined for a target variable is not the same as
the length of the corresponding database column. The ASC2Q utility will
automatically change the length to match that of the database column.
Correction
Run Q2ASC on the new form file. Then compare the old and new ASCII
files to verify that the changes made are appropriate.
If ASC2Q displays this message when you convert a Release 1 ASCII
form file to a Release 2 form file, run Q2ASC on the new form file, then
run ASC2Q on the new ASCII file.
9320
184
Warning, column_name was not a target column in the target table,

but is now.
Explanation
A variable defined as a non-target field in the ASCII form file is actually

a target variable. ASC2Q will automatically change the field to be a target
field.
Correction
If you do not want the specified column to be treated as a target field, use
AGEN to change the name of the field so that its name is not identical to
a database column name.
9321
Explanation
Correction
9322
Explanation
Correction
9323
Warning, old rhli type encountered for column_name, ascii file

needs to be upgraded.
The ASCII form file contains a reference to an old RHLI data type. These
data types are no longer used.
Run the TRAN utility on the ASCII form to upgrade all the FIELD
definitions to Release 2.0 syntax.
Field array cell subscript out of bounds: array_name.

An array subscript was out of the arrays bounds in the ASCII form file.
Change either the array definition to extend the arrays bounds or the
array cell subscript to reference a cell in the arrays bounds.
FIELD_CLASS statement for an undefined array: array_name.
Explanation
The array referenced in the ASCII form files FIELD_CLASS statement

has not been defined in the array definition section.
Correction
Either change the array in the FIELD_CLASS statement to an array that

has been defined or define a new array in the array definition section.
9324
Explanation
Correction
9325
Explanation
Correction
Unexpected field input length specification encountered.

The program_name utility found an input length specification for a
TEXT field. The input length for TEXT fields is unlimited and should
not be specified.
Do not specify an input length value for a TEXT field.
Unexpected field window height specification encountered.

The program_name utility found a window height specification for a
non-TEXT field. Only TEXT fields can have a window height value
specified.
Do not specify a window height value for a non-TEXT field.
185
9701
Explanation
Correction
9709
Explanation
Correction
9710
Explanation
Correction
9726
Explanation
Correction
186
Invalid error number

No corresponding error message was found.
Make sure that a unify.cmf or unify.msg file exists and is readable in the
directory specified by the UNIFY configuration variable. If the file exists
and is readable, contact Unify Customer Support.
Insufficient memory available.

Not enough memory is available to continue.
Reset memory utilization parameters to reduce the overall memory
requirements of the program.
Unknown or invalid value in switch.

This is an internal error and should not occur during normal execution.
file open error:

There has been an error opening the unicap file.
Make sure that the UNICAP configuration variable is set correctly and
that you have read permissions for the unicap file.
ACCELL/SQL Report Writer (RPT)

Error Messages
The following messages may be displayed while you are using the
ACCELL/SQL Report Writer, RPT. For information about using RPT to
write report scripts, see

.
10131
Explanation
Correction
10132
Explanation
Correction
10133
Explanation
Correction
10134
Explanation
Correction
The create on intermediate file file_name failed.

The RPT intermediate file named file_name could not be created.
Make sure that the file exists, that you have read and write permission on
the file, and that the file is in the directory. Make sure that i-nodes are
available in the file system.
The create on tag file file_name failed.
The RPT tag file named file_name could not be created.
Make sure that the file exists, that you have read and write permission on
the file, and that the file is in the directory. Make sure that i-nodes are
available in the file system.
An error was encountered writing to the intermediate file
file_name.
An attempt has been made to write to the file_name file.
Make sure that space is available in the file system.
Invalid column number column_number generated by print
statement on line line_number.
The column number that was specified in the in column clause of the
print statement is greater than the set page width. The line number
line_number identifies the approximate location of the print statement;
the actual statement can occur before the line number indicated.
Increase the width for the report by modifying the width statement or
change the column position in the print statement.
ACCELL/SQL Report Writer (RPT) Error Messages
187
10135
Explanation
Correction
10136
Explanation
Correction
The input line buffer is too small.

A line in the input was too large to fit in the input line buffer.
Increase the input line buffer by setting the RPTINBUFSZ internal table.
There is a phase error in the input file.

The format of an input line does not match the input section of the
script. For example, the input line may contain more or less fields than
are declared in the input section of the RPT script.
Examine the input file for extra values on each line. Make sure that each
line of the input file contains a value for each input column listed in the
input section. Also verify that the data types of the value and the input
column match.
Look for non-escaped separator characters, such as | or \, embedded
in a column value. For example, if a | character is embedded in a string
column, RPT interprets the character as the end of the column, so that the
remainder of the column is interpreted as the next column.
10137
Explanation
Correction
10138
Explanation
Correction
188
Insufficient memory for argument list.

When describing a user function call in a script, too many arguments
were used to call the function.
Use fewer arguments or reset the RPT internal tables to reduce the
overall memory requirements for the script.
There is insufficient memory for the output line buffer.

Not enough memory is available for the buffer to print an output line.
Use the width statement to decrease the output width, if possible, or
reset the RPT internal tables to decrease the amount of memory allocated
for the various tables.
10139
Explanation
Correction
There is insufficient memory to hold variables.

Not enough memory is available to store all the variable values.
Increase the number of variables allowed by setting the RPTFLDCNT
internal table. To reduce the total memory requirements, try one of these
solutions:
Decrease the lengths of output strings and report columns.
Decrease the number of variables.
Reduce the complexity of the report script.
10140
Explanation
Correction
10141
Explanation
Correction
There are no input records

The specified input file is empty.
Verify that the specified file exists, is readable, and contains the
appropriate data.
The open on tag file file_name failed.

RPT cannot open the tag file (file_name) that has already been created.
Make sure the file_name file exists. It may have been removed by
another user.
10142
There was an output width overflow from the print expression on

line line_number.
Explanation
The print expression on line line_number tried to print past the report
width.
Correction
Try one of these solutions:

Increase the output width.
Reduce the size of the information being output.
Break the information into two or more lines.
Move the information to the left on the line (reduce its col
position).
189
10143
Explanation
Correction
10144
Explanation
Correction
10145
Explanation
Correction
10146
Explanation
Correction
10150
Explanation
Correction
190
There is a saved string overflow.

An excessively long string is being formatted by the using option of the
print statement.
Try reducing the length of the input string.
There are too many saved strings.

Too many strings are being formatted with the using option of the print
statement.
Reduce the number of using formats in the report print statements.
Internal error: Unexpected command type number in docom.

This is an internal error and should not occur in the normal execution of
an RPT script.
Unable to execute the sort command.

RPT could not execute the system sort command.
Make sure that the UNIFY configuration variable is set correctly. Also
verify that the sort command is in your directory search path (specified
by the PATH configuration variable).
Type conversion error. Left type is type1, right type is type2, operator
is operator.
The data types of the type1 and type2 operands in the expression do not
match and cannot be converted.
Make sure that you have used the correct column and variable names.
Change the operands so that their data types are compatible.
10151
Explanation
There is an assignment to a nonvariable on line line number.

An attempt has been made to set the value of an input column on line
line_number. You cannot use the same name for a variable and an input
column in the same report script.
Correction
Make sure you are not setting the value of an input column. Choose a
different name for either the variable or the input column.
10152
Name in the section header on line line_number is not an existing

sort expression.
Explanation
Correction
10158
Explanation
Correction
10159
Explanation
Correction
10160
Explanation
Correction
A before or after section on line line_number of the report script is

referring to a name that is not listed as a sort element.
Add the name to the sort list or remove the incorrect section.
An explicit column position was combined with the centered

keyword.
You cannot use both the centered keyword and an absolute column
position.
Remove either the column position or the centered keyword.
The if clause on line line_number does not contain an integer

expression.
RPT could not recognize the expression in the if statement on the line
line_number.
Make sure you use a relational operator in the if expression.
Unrecognized type in set statement. Expression type type1, variable

type type2.
An attempt has been made to set a variable to an unrecognized data type
in a set statement.
Correct the part of the statement that has the unrecognized data type.
191
10161
Explanation
Correction
Input column table.column_name does not have its type specified,

and it is not a database column.
RPT could not find the column table.column in the database.
If the input column is an arbitrary name, you may have omitted the data
type and length specification.
If this input column is a database column name, make sure that the
configuration variables describe the correct database. Also, make sure
that the column name is spelled correctly and is sufficiently qualified so
that it is not ambiguous.
If the input column name is correct, make sure that the database type is
correct, and on systems that require users to log into the database, make
sure that the user name and password are valid.
10162
There is insufficient memory for the input columns.
Explanation
Not enough memory is available to process your report.
Explanation
Increase the size of the input buffer by setting the RPTINBUFSZ internal
table. You may need to decrease another table size as well. To reduce the
total memory requirements, try one of these solutions:
Decrease the lengths of output strings and report columns.
Decrease the number of variables.
Reduce the complexity of the report script.
10163
Explanation
Correction
10164
Explanation
Correction
192
Illegal use of variable variable_name.

The variable_name variable cannot be used in this context. This error
can occur as the result of a misspelled function, keyword, variable, or
column name.
Do not use a local variable in this context. Also, make sure that the
variable name is spelled correctly.
There is a type mismatch in the set statement on line line number.
The variable type is type1 and the expression type is type2.
An attempt has been made on line line_number to assign a value of an
incompatible data type to a variable that has already been set.
Use a different local variable for the new data type.
10165
Explanation
Correction
10167
Explanation
Correction
10169
Explanation
Correction
10170
Explanation
Correction
10171
Explanation
Correction
There is a nested aggregate operator on line line_number.

An attempt has been made on line line_number to use an aggregate
function as an argument for another aggregate function.
Assign the aggregate function value to a variable and use this variable as
the second aggregate functions argument.
There is an aggregate expression embedded in a sort expression on

line line_number.
An attempt has been made on line line_number to use an aggregate
function in a sort expression.
Remove the aggregate function from the sort expression.
There is a variable used in a sort expression on line line number.

An attempt has been made on line line_number to use a variable as a sort
element.
Make sure that you have not used variables as sort elements and check
for misspellings in the sort statement.
Function_name is an unrecognized function name.

The function_name function does not exist or cannot be read.
Make sure that the function name is spelled correctly.
Internal error: Unexpected type in comptyp type.

an RPT script.
193
10173
Explanation
The value of variable variable_name is never set.

This error can be caused by one of the following conditions:
The variable_name variable should be a string, but the required
quotes have been omitted.
The value of the variable_name variable has not been initialized
with a set statement
The variable has not been included as a input column in the input
section.
Correction
10174
Explanation
The width has been set to a value less than or equal to the left
margin.
The width must be set to a value larger than the left margin value.
Correction
Increase the width or decrease the left margin.
10176
Internal error: Unrecognized style in settyp.
Explanation
an RPT script.
Correction
10181
Unable to open specified input file file_name.
Explanation
Correction
10204
Explanation
Correction
194
Make sure that the variable is not supposed to be a quoted string. If it is

not a string, make sure that the variable name is spelled correctly.
Initialize the variable or correct the syntax error.
RPT could not find or open the input file file_name.
Make sure that the file name is spelled correctly and that the file has the
correct read permission.
Unrecognized character: character.
RPT could not recognize the character character.
If the character is part of a string constant, insert the missing single

quote. If the character is not valid, remove it.
10205
Explanation
There is an invalid non-section statement.

This error can be caused by the following conditions:
misspelling a statement keyword
omitting a comma
trying to print a multiple-word heading without enclosing it in
single quotation marks
omitting the end statement to terminate the report script
not putting the set statement in a section
Correction
10206
Explanation
Correction
10207
Make sure that the RPT script does not contain any of the preceding
syntax errors in a non-section statement.
An integer constant was expected.

The syntax for the statement requires an integer constant.
Make sure that an integer constant is specified.
A sort command is not allowed on presorted input.
Explanation
An attempt was made to use both the sort statement and the sorted
option. RPT does not allow the sort statement to be used when the
sorted option is used with the input statement.
Correction
Either remove the unnecessary sort statement or remove the sorted

keyword from the input statement.
10208
Explanation
Correction
A string constant was expected.

The syntax for the statement requires a a string constant enclosed in
single quotation marks (constant).
Make sure that the constant value is not missing one of the single
quotation mark.
195
10209
Explanation
Correction
10210
Explanation
There is an invalid input item.

RPT could not recognize an input column name in the input statement.
This error can also be caused by including a comma after the last input
item. RPT then reads the next line as part of the input statement.
Make sure that you are not using an RPT keyword or function name as
an input column name. Also make sure that there is no comma at the end
of the input statement.
There is an invalid type expression.
RPT could not recognize the data type of an input column listed in the
input statement.
Correction
10211
Explanation
Correction
10212
Explanation
Correction
10213
Explanation
Correction
196
Make sure that input column data types are specified with the correct
data type keyword spelling.
There is an integer constant expected for the length.
An attempt was made to specify a non-integer length for an input
column. When a data type and length is assigned to an input column in
the input statement, the length must be an integer.
Use an integer to specify the input column length.
There is an invalid statement.
RPT could not recognize the word as a section identifier.
Often this error is caused by a misspelling of the first word on a

statement line following a section statement.
There is an error in an if expression.
RPT found an incorrect expression in an if statement.
Examine the syntax of the if statement to make sure that the if, then, and
else keywords are used correctly. For the syntax and usage description of
the if statement, see

.
10214
Either desc or a named expression was expected.
Explanation
RPT found a syntax error in a sort statement or in one of its expressions.
Correction
Look for an extra comma at the end of the sort statement. For the syntax
and usage description of the sort statement, see

.
10215
Explanation
Correction
10216
Explanation
Correction
10217
Explanation
Correction
10218
Explanation
There is an invalid print item.

RPT found a syntax error in a print expression.
Make sure that the print expression does not contain keywords. To print
out the string value for a keyword, you must enclose the word in single
quotation marks (word). For the syntax and usage description of the in
column clause in the print statement, see

.
There is an invalid in column clause.
An integer constant or variable must follow the in column clause.
Examine the print statement for a missing position value in the in
column clause. For the syntax and usage description of the in column
clause in the print statement, see

.
There is an invalid using clause.
RPT found a syntax error in the using clause of a print statement.
Examine the syntax of the using clause in the print statement. For the
syntax and usage description of the using clause in the print statement,
see
.
There is an invalid aggregate expression.
RPT found a syntax error for an aggregate expression in an aggregate
function.
Correction
Examine the argument list for an invalid aggregate expression. For

information about using aggregate expressions in report scripts, see

.
197
10219
Explanation
Correction
10220
Explanation
Correction
10230
Explanation
Correction
There is an invalid function argument list.

RPT found a syntax error in the argument list of a function.
Examine the argument list for a missing parenthesis, a missing comma,

or missing single quotation mark.
Unable to open script file file_name.

RPT could not find or open the file_name report script file.
Make sure that report script file name is spelled correctly and that the file
has correct file permissions.
The internal_table_name table has overflowed.

The capacity of the internal_table_name table has been exceeded.
Reduce the number of elements of the indicated type in the script or
increase the size of the indicated table by using the specified
internal_table_name.
For example, the following message indicates that you should either
reduce the number or size of the string constants in the script or increase
the size of the RPTCONCNT internal table.
The String table has overflowed
10231
There is insufficient memory to store the constants.
Explanation
Not enough memory is available to store all data associated with the
print statements.
Correction
Increase the number of constants allowed by using the RPTCONCNT

internal table, or reduce the total memory requirements by
decreasing the lengths of output strings and input columns
decreasing the number of variables
reducing the complexity of the report script
198
10250
Explanation
Correction
10260
Explanation
Correction
10261
Explanation
Correction
10263
Explanation
Correction
10264
Explanation
Correction
10265
Explanation
Output width overflow from function function_name.

an RPT script.
Operator not found.
an RPT script.
Unknown string expression type.
an RPT script.
Unexpected type in intsize number.
an RPT script.
Unable to execute FNDFLD error_message.
RPT could not execute the FNDFLD program. The following error
message provides more information on the problem.
Make sure that the UNIFY configuration variable is set correctly. Also
make sure that the FNDFLD program is on the directory search path
specified by your PATH configuration variable.
The write to FNDFLD failed error_message.
RPT could not write to the FNDFLD program. The specified error
message provides more information about the problem.

Correction
Make sure that the UNIFY configuration variable is set correctly and that
there is write permission on the directory.
199
ACCELL/SQL Menu Handler Error

Messages
The following messages may be displayed while you are using
ACCELL/SQL Menu Handler.
10763
Explanation
Correction
10767
Explanation
Correction
10788
There are no options on that menu.

The menu selected does not have any options registered on it, or the user
does not have privileges to execute any of the options.
Remove the empty menu from the Menu Handler system, or register
options on the menu. For information about adding, modifying, and
deleting menus, see .
Unable to find help documentation for this selection.

A Menu Handler help file was not found.
For information about locating and creating help documentation, see
.
Unable to find default schema, syncauth may need to be run.
Explanation
The schema is the database object that contains the files to be used. In
this case, Menu Handler could not find the database object that was
specified on the command line or the users default. This database object
is a database, user, or schema, depending on the RDBMS on which
Correction
If the database object is specified on the command line, make sure that it
is spelled correctly. Otherwise run the syncauth utility and try again.
For the syntax and usage description for the syncauth utility, see

.
200
ACCELL/SQL Menu Handler Error Messages
10812
Explanation
Correction
Unable to find menu/program by that name.

The specified executable name was not found.
Make sure that the executable name is spelled correctly. Try fully
qualifying the name as schema_name.!executable_name.
The schema is the database object that contains the files to be used. This
database object is a database, user, or schema, depending on the RDBMS
on which ACCELL/SQL is running.
ACCELL/SQL Menu Handler Error Messages
201
ACCELL/SQL RDBMS Interface Error

Messages
If the message applies to a specific RDBMS only, the associated RDBMS
will be indicated below the message text, as shown in this example:
-11299
An unrecognized database error has occurred.

(SYBASE SQL Server only)
Tip
If you have an unexplained error while running an ACCELL/SQL
application on the SYBASE SQL Server RDBMS, determine whether your
syslog is full. After many operations, your database syslog can fill. A full
syslog can cause unusual behavior while running ACCELL/SQL .
11200
Explanation
Correction
11201
The database has sent an error code that ACCELL/SQL does not
recognize.
Determine which database operation is involved, then contact Unify
Customer Support.
An internal database error has occurred.
Explanation
An internal error has occurred, although this type of error should not
normally occur.
Correction

Customer Support.
11204
Explanation
Correction
202
An unrecognized database error has occurred.
No space in db for some resource.

The database has run out of resources. This error is probably because the
maximum number of tables, columns, buffers, indexes, partitions, or files
has been exceeded, or the maximum amount of space has been exceeded.
Determine which resource has been exhausted. Follow instructions in
your RDBMS manuals to increase the resource, then try the operation
again.
ACCELL/SQL RDBMS Interface Error Messages
11206
Binding error.
Explanation
An internal error occurred while performing a bind operation in the

ACCELL/SQL RDBMS interface.
Correction

Customer Support.
11207
Explanation
Correction
11209
Explanation
Illegal reference of an unusable view.

The attempted operation was not valid for the specified view. For
example, a delete operation was attempted on a view that cannot support
this operation.
Determine which database operation is involved. Then either change
your ACCELL/SQL application so that it does not perform the invalid
operation, or change the application so that it operates on a database
object where the operation is valid.
Database has been modified.
The database design has been modified since the ACCELL/SQL
application was built and is incompatible with the application. For
example, a target table may have been dropped, or a column data type
may have been changed.
Or you may be accessing the database from the wrong database object.
This database object is a database, owner, schema, or user, depending on
the RDBMS on which you are running ACCELL/SQL .
Correction
Try one or more of these solutions:

Make sure that you are using the correct database.
Make sure that no one else is modifying the database design while
you are using it.
Make sure that the data types of target fields and other database
variables match the data types of the corresponding database
columns.
Make sure that you are running under the correct database, owner,
schema, or user, depending on the RDBMS.
Make sure that you have logged in correctly, if you are running on
a system that requires you to log into the database.
203
11211
(Unify DataServer only)
Explanation
A list element in an RHLI status list was valid but that no action was
taken due to an error in another element of the list. This error is usually
accompanied by another error in the status list.
Correction
Check the status list errors. Find the RHLI function that causes the error
and correct the offending list element.
11213
Explanation
Correction
11214
Explanation
Correction
11215
Explanation
Correction
11216
Explanation
Correction
204
Valid, but no work was done.
Database interface internal error.

The ACCELL/SQL RDBMS interface is using the database in an invalid
way.
Customer Support.
Error accessing network.
An RDBMS network error has occurred.
Make sure that you are running the correct version of the RDBMS
software and that the network hardware and software are working
correctly. Also, make sure that C-hook functions call the RDBMS
interface with the correct variables and valid, initialized data.
Deadlock error, transaction rolled back.
Deadlock has occurred because two or more users are waiting for
resources that cannot be freed because they are held by the waiting users.
The RDBMS has detected this situation and aborted your transaction.
Repeat all the operations in the aborted transaction.
B-tree Manager Cannot open Database.
An attempt has been made by the B-tree index manager to open a B-tree
index file that does not exist, or does not have valid read/write
permissions. This is an internal error and should not occur in the normal
execution of the database.
11218
Explanation
Correction
11219
Wrong number of columns returned from a stored procedure.

The stored procedure call performed a select that returned a different
number of columns from the number expected.
Correct the stored procedure call so that the number of columns expected
is the same as the number of columns returned.
Missing parameter to a stored procedure.

Explanation
UNDEFINED was specified as an argument to a stored procedure that did

not have a default defined for that argument. UNDEFINED can be used as
an argument only when a default is defined.

Correction
11222
Explanation
Correction
11223
Explanation
Correction
11225
Explanation
Correction
Fix the application so that it does not pass UNDEFINED unless the
argument has a default.
Duplicate Row ids found.
Some database rows have duplicate row IDs.

Run the ridutil utility to reset the row IDs so that none are duplicated.
System log is full.
The SYBASE SQL Server system log is full.

Dump the transaction log as directed in your SYBASE SQL Server system
administration manual.
Implicit conversion error.
The types of arguments in a stored procedure call do not match.

Verify that the arguments in all stored procedure calls match the stored
procedure definitions.
205
11226
Explanation
Correction
11227
Explanation
Correction
11228
Explanation
Operand type clash.
The types of arguments in a stored procedure call do not match.

Verify that the arguments in all stored procedure calls match the stored
procedure definitions.
A column insert or update conflicts with a rule.
The user has entered data that violates the rules set in the SYBASE SQL
Server RDBMS for this database field.
Enter data that does not violate the rules for this field.
User defined error.
A print or a raiserror was issued but did not indicate a rollback and did
not give any message text with the error.
This error message displays only if the error resulted from an interactive
operation.
Correction
11229
Explanation
Correction
Use the status$() system function to determine whether a rollback

occurred. The system status code is set to SS_UDERB if a rollback
occurred, or SS_UDE if no rollback occurred.
User defined error.
A print or a raiserror error was sent to ACCELL/SQL . The error did not
indicate that a rollback occurred, but it did include text with the error
number.
Verify that your input is correct. If the input is correct, work with your
application administrator to determine the source of the error.
If the error resulted from a raiserror call during an interactive operation,
the text and error number sent by raiserror are displayed in this error
messages error window.
If the ACLDBDBG configuration variable is set to a file name, the print
or raiserror information is printed in the specified file. The ACLDBDBG
configuration variable is described in Configuration Variable Reference
in
.
206
11230
User defined error for rollback.
Explanation
A raiserror error was sent to ACCELL/SQL . The error indicated that a

rollback occurredthe current transaction was aborted. Any work
completed within the current transaction has been undone and must be
re-entered. A new transaction has been started.
Correction
Work with your application administrator to determine the source of the

error. If the error occurred during an interactive operation, the text and
number associated with the error are displayed in this error messages
error window.
If the ACLDBDBG configuration variable is set to a file name, the print
or raiserror information is printed in the specified file. The ACLDBDBG
configuration variable is described in Configuration Variable Reference
in
.
11232
Explanation
Correction
11237
Explanation
Correction
11238
Explanation
Correction
User benign rollback.
A raiserror error was sent to ACCELL/SQL to indicate that a rollback

occurred. However, the user indicated that the error is to be ignored (as
defined by the SYBASE_RB_RESTART configuration variable).
ACCELL/SQL must first restart the ACCELL/M anager transaction before
the error can be ignored.
Object name is ambiguous or multiply defined.

The specified object name was ambiguous because it could refer to more
than one object.
Use a more fully qualified name.
Column not found in table.

The database has been modified since this application was built.
Make sure that you are referencing the correct database. Also make sure
that the target table contains matching columns for all target fields
defined for the current form.
207
11240
Explanation
Internal error accessing ASQLCRSR pool.

ACCELL/SQL uses internal structures to store information on its
currently active cursors. This error indicates that an internal

ACCELL/SQL error has occurred in the management of these structures.
Correction
11241
Explanation

Internal error accessing ASQLINFO pool.
ACCELL/SQL uses internal structures to manage memory used to process
an SQL command. This error indicates that an internal ACCELL/SQL
error has occurred in the management of these structures.

Correction
11247
Internal error, invalid SQLID.

(SYBASE SQL Server and Unify DataServer only)
Explanation
ACCELL/SQL uses internal structures to manage memory used to process

an SQL command. This error indicates that an internal ACCELL/SQL
error has occurred in the management of these structures.

Correction
11248
Explanation
Correction
11249
Explanation

The number of columns returned does not match the number
expected.
When the record was fetched from the database, the number of columns
returned did not match the number expected. This error indicates that an
internal ACCELL/SQL error has occurred.
Internal error, ACCELL/SQL type not supported by database.
ACCELL/SQL maps each of its various data types to one of those of the
underlying RDBMS. An invalid ACCELL/SQL type was found when
doing this mapping. This error indicates that an internal ACCELL/SQL
error has occurred.

Correction
208

11250
Explanation
Correction
11251
Explanation
An undefined ACCELL/SQL variable can not be used in an SQL

statement.
An UNDEFINED value was encountered when processing a stored
procedure call, or when building an SQL Server command to be sent to
the RDBMS.
Determine which value is UNDEFINED and set it to a defined value.
Internal error, unsupported database type.
ACCELL/SQL maps each of the data types of the underlying RDBMS to
one of its own data types. A database type that is not mapped to an
ACCELL/SQL type (is not supported by ACCELL/SQL ) was found.
Correction
11253
Remove the reference to the column that has the unsupported data type.
Internal error, unknown signal.
Explanation
ACCELL/M anager found an unknown signal in the interrupt handler area.
Correction
If this error occurs, please call Unify Customer Support. For information
about using the set_interrupt$( ) system function to turn interrupts on
and off, see

.
11254
Explanation
Correction
11255
Explanation
Correction
Out of heap memory.

ACCELL/M anager keeps a variety of internal information in an area
called the heap. The current heap size is too small to run the current
application.
To increase the heap size, set the AMGR_HPSZ configuration variable to a

higher value. AMGR_HPSZ is described in

.
Out of memory.
ACCELL/M anager has run out of memory.

209
11256
Explanation
Open/create of text/binary data file failed.

ACCELL/SQL stores TEXT and BINARY values that have lengths greater
than the value specified by the ACLVARMEMLIM configuration variable
in temporary files. An attempt to open or create a one of these files

failed.
Correction
Make sure that the directory specified by the ACLVARDIR configuration

variable exists and that the permissions allow write access to the current
user. Also make sure that you are not out of disk space and that the
number of variable length data files being used by the application is not
excessive.
The ACLVARMEMLIM and ACLVARDIR configuration variables are
described in

.
11257
Close of text/binary data file failed.
Explanation
in temporary files. An attempt to close one of these files failed.
Correction
Make sure that you have enough disk space. If you have plenty of disk
space, this error may indicate an internal error, in which case you should
call Unify Customer Support.
Before you call Customer Support, try executing the application with a
larger value for the ACLMXOPNVARF configuration variable.
The ACLMXOPNVARF configuration variable is described in

.
210
11258
Explanation
Correction
Read of text/binary data file failed.

in temporary files. The user can also read TEXT and BINARY values
from user files by using the RETRIEVE statement. An attempt to read or
access one of these temporary or user files failed.

configuration variable exists and that the permissions allow read
access to the current user.
If the offending ACCELL/4GL statement is a RETRIEVE
statement, make sure that the specified file exists and that the
permissions allow read access.
If the application contains C functions that adjust the length stored
in the AVAL structure for TEXT or BINARY values, make sure that
the lengths are set correctly.
described in

.
11259
Explanation
Correction
Write of text/binary data file failed.

in temporary files. The user can also store TEXT and BINARY values in
user files by using the STORE statement. An attempt to write to one of
these temporary or user files failed.
Try one or more of the following solutions:

configuration variable exists and has the correct write permissions.
If the offending ACCELL/4GL statement is a STORE statement,
make sure that the user has write access for the file to be written
to.
Make sure that you have not run out of disk space.
described in

.
211
11260
Explanation
Transaction aborted by SQL Server.

This message is displayed if SYBASE SQL Server aborts the current
ACCELL/SQL transaction. Usually this error occurs because of some flaw
in your application program logic. Specific information about the cause
of the error is in the file specified by the ACLDBDBG configuration
variable, if it is set.
This message also produces the following interactive message:
Your ACCELL transaction has been aborted
by SQL Server due to a severe error.
All work done since starting the current

transaction has been lost.
After the message is displayed, ACCELL/SQL restarts the users
transaction and continues.
Correction
11270
Explanation
Correction
11275
Explanation
Correction
212
After determining the cause of the error, rewrite the portion of your
application that is causing the problem.
Transaction has no locks.

the database.
A null value was specified for a column with the not-null attribute.
An attempt has been made to insert or update a columns data value to
null when the column has been specified as NOT NULL.
Make sure that the valopts field of the UNIPCOLL structure is correctly
initialized before performing the insert or update operation. Non-null
default values can be assigned to null columns using the Data Integrity
Subsystem (DIS).
11276
Explanation
Correction
11278

The ASCII value provided for conversion to a database type is not valid
for the specified type. For example, this error can occur if non-numeric
characters are provided for a numeric column.
Either provide a valid ASCII value or change the destination type to
something that will allow the data provided.
Compiled object does not match mapped object.

only)
(Unify DataServer
Explanation
An attempt has been made to map a compile-time ID to a runtime object

whose MAPID no longer reflects the same physical characteristics as the
compile-time object. The runtime object has probably had schema
modifications made to it since the compile-time object was referenced.
Correction
The application source files that reference the object need to be

recompiled using the ucc utility, and relinked using the uld utility.
Depending on the changes made to the object, source code modifications
may be necessary.
11279
Explanation
Correction
11280
Explanation
Correction
Invalid name (Name not supplied or name contains reserved

characters).
The database object name specified included reserved characters or was
of zero length.
Correct the object name.
Scan (or ordered access) ID is not found (Has the scan been closed?).
An attempt has been made to reference a Scan ID that does not exist.
Make sure that the Scan ID was returned from a successful RHLI
ubegscn function call. Also make sure that this scan was not closed with
the RHLI uendscn function call.
213
11281
Explanation
Correction
11282
Explanation
Correction
11283
Explanation
Correction
11284
Explanation
Correction
11285
Explanation
Correction
214
Bad selection criteria.

the database.
Column type mismatch.

An attempt has been made to reference an index using columns that do
not match the columns used to create the index.
Make sure that the Column IDs match the Column IDs used to create the
index. Make sure that the Column IDs do not reference a column group.
Unable to back out operation fatal.
(UNIFY 2000 only)
The database system detected an internal, non-recoverable error while

trying to back out a failed operation. See the errlog file for an entry
describing the cause of the error.
Recover the database using the irma utility.
Fatal error in B-tree access; rebuild.

An internal error was detected while scanning a B-tree index. This is an
internal error and should not occur in the normal execution of the
database.
Error opening B-tree.

The system was unable to open a B-tree index file.
Make sure that the B-tree index file has not been removed. If the B-tree
index file exists and you still receive this error, please call Unify
Customer Support.
11286
Explanation
Correction
11287
Explanation
Correction
11288
Explanation
Correction
11289
Explanation
Correction
11290
Explanation
Correction
Combination group not allowed.
An attempt has been made to reference a Column Group ID, instead of

the component members Column IDs. In most RHLI functions, the
Column Group ID may not be referenced.
Use the Column IDs for the member columns in the column group.
Internal cache manager error (nonfatal).

the database.
Data value conversion error.

An attempt has been made to perform a an invalid data conversion. This
error occurs when the data to be converted does not conform to the
constraints for the columns data type. For instance, the date 88/88/88
would produce this error because the month 88 is invalid.
Make sure that the data to be converted conforms to the columns data
type restrictions.
Conversion error.
the database.
Sort/merge file open/creation failed.

Failed to create or open a sort/merge file. You may have run out of file
descriptors.
Manage your file descriptors so that you dont exceed the limit. You may
want to reconfigure your operating system if you encounter a consistent
shortage of file descriptors.
215
11291
Explanation
Correction
11292
Explanation
Correction
11293
Explanation
Correction
11294
Explanation
Correction
11295
Explanation
Correction
216
Database is closed; attempt to access database which is not open.

An attempt has been made to access a database that has not yet been
opened or that has since been closed.
Perform the operation after the database has been opened and before the
database has been closed. Make sure that the open database operation
succeeded before attempting other database activities.
The column data type internal length is larger than maximum

length.
An attempt has been made to specify an internal column data type length
that is larger than the maximum allowable data length.
Check the restrictions for the data types that you are using.
Generic operating system error.
An operating system error has occurred that cannot be mapped to a

standard RHLI error.
Try to determine the statement of statements causing the error. Examine
the error that occurred just after this one, if any.
Duplicate key found in No duplicate B-tree.

An attempt has been made to insert a duplicate key into a B-tree that
does not allow duplicates. This row must already exist in the B-tree.
You cannot add the duplicate key into the B-tree. If you want to add this
duplicate key, you must rebuild the B-tree, allowing duplicates.
Configuration variable Bad format.

the database.
11296
Explanation
Correction
11297
Explanation
Correction
11298
Explanation
Correction
11299
Explanation
Correction
11300
Explanation
Correction
Configuration variable not found.

the database.
End of scan (or ordered access).

The end of the selected set of rows has been reached, and no more rows
remain to be retrieved.
No correction needed.
An invalid memory address was supplied as a parameter to an RHLI

function.
An RHLI function was called with an invalid memory pointer.
Verify the parameters passed to the RHLI function. Check the placement
of pointer references.
Denied access to file.

An attempt has been made to access a database file for which the process
does not have access permission. This is an internal error and should not
occur in the normal execution of the database.
Failed to close a file.

An attempt has been made to close a file that is already closed. This is an
database.
217
11301
Explanation
Correction
11302
Explanation
Correction
11303
Explanation
Correction
11304
Explanation
Correction
11307
Explanation
Correction
218
File create error.

An attempt has been made to create a volume file that already exists.
If you still want to create a new volume file, remove or move the file that
currently exists before creating the volume.
Partial success; see the individual status list.
One or more errors occurred on multi-valued parameter; the actual errors

are contained in the status list that was passed to the function.
Examine the RHLI functions status list to determine the actual errors.
Check for the correct number of parameters.
File seek error.

An attempt has been made to perform a file seek operation on a file that
is not seekable, or with an invalid specified seek address. This is an
database.
Lock granted due to upper level lock.
This is an advisory message that indicates that a lock was granted

because the transaction already holds an enclosing upper level lock. For
example, this message can be displayed when a row lock is requested
while a table lock is already held on the table that contains the row.

The end of the selected set of rows has been reached, and no more rows
remain to be retrieved.
11308
Explanation
Correction
11309
Explanation
Correction
11310
Explanation
Correction
Illegal argument.
An attempt has been made to specify an option that is invalid or conflicts
with another specified option. This is an internal error and should not
Illegal test for value type.

the database.
Illegal transaction ID.
(UNIFY 2000 only)
The database failed to validate a Transaction ID.

Check the validity of the Transaction ID passed to an RHLI function in
your program.
Also, check that the logical log file (file.lg) is not running out of space.
Your transaction could have been aborted if it was the oldest open
transaction in the log and another transaction needed space in the log.
11311
Explanation
Correction
11312
Explanation
Correction
An interrupt has occurred.
This error is returned by most RHLI functions after an interrupt is set by

the default Unify DataServer signal handler or by the function usetitr.
Use the uclritr function to resume processing after the interrupt.
Row does not have read permission.
An attempt has been made to read a row from a volume for which the
user does not have read access. This is an internal error and should not
If this error occurs, please call unify Customer Support.
219
11313
Explanation
Correction
the database.
11314
The column cannot be changed due to references to it.

Explanation
An attempt has been made to delete a row that either has a lock on it or is
a parent link column with existing child links.
Correction
11315
Explanation
Correction
11316
Explanation
Correction
11317
Explanation
Correction
220
Invalid default type.
Delete all of the child table rows before attempting to delete the parent
table row. The rows can be identified using a link scan.
Process terminated at user request (typically using shutdb utility).

Another user has started to shut down the database.
If possible, save your work and exit the database immediately.
Lock Manager initialization failure.
the database.
Key not found.
A duplicate key value is being inserted into a unique-key hash table. The
user may see error 194 (the UENOROW error code), which indicates an
invalid row ID in general (not hash table specific).This is an internal
error and should not occur in the normal execution of the database.
11318
Explanation
Correction
11320
Explanation
Correction
11321
Explanation
Correction
11322
Explanation
Correction
11323
Explanation
Correction
Transaction logging not turned on.
An attempt has been made to request a transaction log operation when

logging is not turned on for the process.
Turn on transaction logging by setting the LOGTX configuration variable
to TRUE and retry the operation.
Too many scans (an/or ordered accesses) active at once.
An attempt has been made to start a scan that would exceed the
maximum number of simultaneous scans permitted per process.
Make sure that scans are properly closed using the RHLI uendscn
function.
Selection table full.
the database.
Could not attach shared memory at required address.
Shared memory could not be attached at the required address. The
required attach address would probably overlap the data space of the
process. This problem is usually caused by starting the database with a
small program, such as shmmap, and later attempting to open the
database with a much larger program, such as SQL or startdb.
Shut down the database and either increase the value of the SHMOFFSET
configuration parameter or restart the database using the larger program.
Invalid column ID/not part of common table. (Unify DataServer only)
An attempt has been made to reference a column ID that does not exist.
This column may have been deleted just before being referenced.
Make sure that the Column ID was obtained using the correct name
binding functions such as the RHLI name binding function ubndcol,
through the RHLI functions such as uinftbl or uinfcol, or through the
ucc compiler.
221
11324
Explanation
An attempt has been made to reference a column group, but the specified
Column IDs do not belong to any known column group. This error
occurs when trying to retrieve rows based on an index key.
Correction
Make sure that the Column IDs are in the same sequence as those used to
create the index. Make sure that the specified number of columns
matches the number specified when the index was created.
11325
Explanation
Correction
11326
Explanation
Correction
No current row for CROW type default.
the database.
No current row for column type default.
the database.
If this error occurs, please call unify Customer Support.
11327
The database root volume (i.e. file.db) cannot be accessed.

Explanation
The Unify DataServer database system is unable to open the database root
volume.
Correction
Make sure that the DBPATH and DBNAME configuration variables are set
correctly. Make sure that you have the required operating system
permissions on the file.
11328
Explanation
Correction
222
Not a column group.
The row was NOT deleted.
(UNIFY 2000 only)
An attempt has been made to insert a row into a direct table, where the
specified primary value was mapped to a row that already exists. You can
only insert rows into a direct table at locations occupied by deleted or
non-existent rows. This error only occurs when the primary key value is
specified in the UNIPCOLL data structure.
Use an update operation to update a direct table row.
11329
Explanation
Correction
11330
Explanation
Correction
11331
Request was not a demotion request.

the database.
No default for this column.

the database.
Transaction logging has not been enabled transactions cannot be

aborted.
Explanation
An attempt has been made to abort a transaction when the transactions

are not logged.
Correction
To be able to abort future transactions, turn on transaction logging by

setting TXLOG configuration variable to TRUE. You can commit
transactions instead of aborting, but the updates affect the database.
11332
Explanation
Correction
11333
Explanation
Correction
No such file, directory, or program.
This error occurs when a file name is specified and the file does not
exist, or when one of the directories in a path name does not exist.
Check the errlog file to determine which file could not be found. Also,
check the error message documentation for error number 2 in your UNIX
system documentation.
File does not exist.

An attempt has been made to open a file that does not exist. This is an
database.
223
11334
Explanation
Correction
11335
Explanation
Correction
11337
Explanation
Correction
The software version that created the shared memory was not the same
version as the current software or the shared memory segment is not a
Unify DataServer shared memory segment.
Make sure that the shared memory segment being used is a Unify
DataServer shared memory segment. If not, you probably need to change
the shared memory key, SHMKEY, to a value unique to this software.
Key column(s) required.
An attempt has been made to perform an operation requiring a primary
key column on a table that does not contain a primary key.
Add a primary key column to the table, or perform an operation that does
not require a primary key column, such as through use of a scan.
Log file does not exist.
The transaction log file does not exist in the DBPATH directory.
Check that the DBPATH environment variable is set correctly. Create the
transaction log file using the mklog utility.
11338
The software version does not match the shared memory version.
Explanation
The software that created the shared memory was not the same version as
the current software.
Correction
Make sure that the correct release of the RDBMS software is being used.
11339
Explanation
Correction
224
The software version does not match the shared memory segment
version.
Object does not exist.

The specified object does not exist or is not permitted to be seen.
If the object is known to exist, your current schema (or database, owner,
or user) may not be permitted to see this object. Assume a schema that
owns the object and try again.
11340
Explanation
Correction
11341
Explanation
No privilege for the attempted operation.

An attempt has been made to perform an operation for which the user has
not been granted the necessary privilege. This error typically relates to
DDL operations performed against a schema the user has not been
granted access to, but the error can also occur by performing DML
operations on tables or columns that are not accessible to the user. In
certain DDL operations, the user is required to be in the schema (or
database, owner, or user) under which the operation is being performed.
Verify and correct access and privileges as necessary.
Privilege does not exist.

This message displays in the following cases:
The current schema (or database, owner, or user) is not permitted
to see the specified objects.
The current schema (or database, owner, or user) cannot add or
drop desired permissions.
(Unify DataServer only) DBA authority is required to run this
utility, as is the case for budb.
Correction
Move to the schema (or database, owner, or user) that owns the object
and retry. Or make sure that you have DBA authority before trying to run
the utility.
11342
Attempt to reference nonexistent row through use of a link.

Explanation
An attempt has been made to insert or update a row containing one or

more columns that are children of links. The corresponding row in the
parent table cannot be found using the value of the child columns data.
Correction
Make sure that the parent tables row containing the data corresponding
to the child columns data has been inserted before inserting or updating
the child columns row.
225
11343
Explanation
Correction
11344
Explanation
Correction
11345
Row does not have write permission.
An attempt has been made to write a row to a volume for which the user
does not have write access. This is an internal error and should not occur
in the normal execution of the database.
Key already exists in hash table.

the database.
Not enough shared memory; try increasing SHMMAX or decreasing

SHMFULL.
Explanation
An attempt to allocate a structure in shared memory failed because the

size of the shared memory segment was exceeded.
Correction
Try to determine which partition is full by using the p option on the

shmmap command. Then use the following table as a guide.
If the full partition is in
the:
Try these steps:
Transaction manager
Reduce the number of active transactions
Lock manager
Reduce the number of locks

Decrease the setting for the LMPROMO
variable
Commit transactions more frequently
File manager
Synchronize the database more often by

adjusting the FREQUENCY and FREQTYPE
variables
Reduce the number of pages modified
between synchronizations
226
If the error persists, try moving the overflowing segment into its own
shared memory area or increasing the associated shared memory
configuration variable (SHMMAX, TMSHMKEY, LMSHMKEY, FMSHMKEY,
CMSHMKEY ).
11346
Explanation
Correction
11347
No space left on device.

No free space remains on the device in which to write an ordinary file.
the database.
Check the error message documentation for error number 28 in your
Unix system documentation.
Invalid table ID.

Explanation
Correction
11348
Explanation
Correction
11349
Explanation
Correction
An attempt has been made to reference a Table ID that does not exist.
Make sure that the Table ID was obtained using the correct name binding
functions such as the RHLI name binding function ubndtbl, through the
RHLI functions such as uinfath, or through the ucc compiler. This table
may have been deleted just before being referenced.
File descriptor not mapped.

the database.
Test requires a value.

the database.
227
Alphabetical Index
Use this index to find messages in alphabetic order by the message text. The message
text is presented, followed by the message number and the page where the message is
described, as shown in this example:
A subtraction operation was attempted on a string value., -8862, 118
Message
text
Message
number
Page
number

'

' is an unrecognized function name., -10170, 192
' ' in the section header on line

is not an existing sort expression., -10152, 189
A bad timer id(s) was encountered in the delete timer statement., -8977, 126
A CLOSE PIPELINE 4GL statement has failed., -8875, 103
A column insert or update conflicts with a rule., -11227, 205
A command sequence is linked to more than one command in the unicap file., -8832, 94
A commit or abort of a transaction has failed., -8941, 117
A CREATE PIPELINE 4GL statement has failed., -8874, 103
A CREATE PIPELINE statement program could not be created., -8878, 104
A division by zero is not allowed., -8817, 92
A field cannot be created on top of existing trim., -9122, 150
A field does not exist at the current position., -9118, 149
A field on this form requires input before the form can be updated., -9146, 155
A field's input length must be greater than zero. Please reenter a value., -9150, 156
A file that was to be created already exists., -9026, 140
A Generator temporary help file could not be opened., -9241, 169
A master application form's NEXT FORM cannot continue a transaction., -8884, 105
229
A null value was specified for a column with the 'notnull' attribute., -11275, 213
A record you are attempting to read has been deleted., -9039, 143
A reference has been made to a non-existent external symbol., -8827, 93
A reference has been made to an invalid screen field name., -8853, 99
A referenced form is not active. The transaction cannot be restarted., -8901, 108
A Row ID is required for the current operation., -9048, 144
A sort command is not allowed on presorted input., -10207, 193
A string constant was expected., -10208, 194
A subtraction operation was attempted on a string value., -8862, 102
A variable's CLEAR_ADD_EXP was set on an invalid form., -9047, 144
ACCELL/SQL cannot run on this size of terminal., -8944, 117
ACCELL/SQL is unable to open the error file ''., -8852, 99
ACMB ERROR: '' used as target table in 4GL, no target table declared in generator., -8319, 13
ACMB ERROR: '' used as target table in AGEN, no target table in 4GL., -8320, 14
ACMB ERROR: '' used as target table in AGEN, used as target table in 4GL.,
-8321, 14
ACMB ERROR: Couldn't find a 'next field'., -8303, 7
ACMB ERROR: The Combine failed in malloc memory., -8302, 6
ACMB ERROR: The DBTYPE configuration variable is not set or is set incorrectly., -8318, 13
ACMB ERROR: The field
is not in the file .[af]q., -8305, 8
ACMB ERROR: The form name has multiple definitions., -8310, 10
ACMB ERROR: There is a corrupt file., -8308, 9
ACMB ERROR: There was a bad magic number., -8301, 6
ACMB ERROR: There was a form name mismatch., -8306, 8
ACMB ERROR: There was a form/application mismatch., -8307, 9
ACMB ERROR: There was an error closing a file, error number ., -8316, 13
ACMB ERROR: There was an error creating '', error number ., -8315, 12
ACMB ERROR: There was an error in adding the form., -8309, 9
ACMB ERROR: There was an error in reading the file ., -8300, 5
ACMB ERROR: There was an error in reading the form., -8311, 11
ACMB ERROR: There was an error opening '', error number ., -8313, 11
ACMB ERROR: There was an error renaming ' ' to ' '., -8314, 12
ACMB ERROR: Type conflict on target variable ., -8317, 13
ACMB ERROR: Warning: there was an illegal display variable name: ., -8312, 11
ACMB ERROR: Checksum error. Verify .fs and .fq target table names match., -8304, 7
ACMB ERROR: Columns in target table '' for .fq and .fo differ., -8323, 14
ACMB ERROR: Number of target columns known to .fq and .fo for table '' do not match.,
-8322, 14

ACMB ERROR: The characteristics of column 'column_name' are different in the .fq and .fo., -8324, 15
ACMB ERROR: The local array 'array_name' was not defined., -8326, 15
ACMB ERROR: There was a class mismatch for field 'field_name'., -8325, 15
ACPL ERROR: A function was redeclared., -8605, 48
ACPL ERROR: A result parameter was expected., -8604, 48
ACPL ERROR: More than one default expression in switch statement., -8601, 47
ACPL ERROR: The number of parameters do not match., -8603, 47
ACPL ERROR: There is an UNDEFINED function., -8602, 47
ACPL ERROR: "IS UNDEFINED" was expected., -8661, 61
ACPL ERROR: 'SET_CONSISTENCY' or 'RECORD_CONSISTENCY' keyword expected., -8613, 49
ACPL ERROR: 'TO' keyword expected after the keywords 'ON CLEAR'., -8607, 48
ACPL ERROR: A "," was expected., -8503, 25
ACPL ERROR: A ";" was expected., -8506, 27
ACPL ERROR: A ":" was expected., -8505, 26
ACPL ERROR: A "(" operator was expected., -8501, 24
ACPL ERROR: A ")" operator was expected., -8502, 24
ACPL ERROR: A 'FIND', 'NEXT' or 'PREVIOUS' keyword was expected., -8614, 49
ACPL ERROR: A button option was expected., -8713, 75
ACPL ERROR: A COMMAND keyword was expected., -8703, 72
ACPL ERROR: A command name was expected., -8705, 72
ACPL ERROR: A field ID was expected., -8524, 29
ACPL ERROR: A file ID was expected., -8525, 30
ACPL ERROR: A form attribute was not expected., -8737, 80
ACPL ERROR: A form code section name was expected., -8569, 40
ACPL ERROR: A form ID was expected., -8526, 30
ACPL ERROR: A form or function name exceeded 15 characters in length., -8504, 26
ACPL ERROR: A form, application or user function definition was expected., -8527, 30
ACPL ERROR: A justification specification was expected., -8533, 32
ACPL ERROR: A LIST array name was expected., -8726, 77
ACPL ERROR: A MATRIX array name was expected., -8727, 78
ACPL ERROR: A PIPELINE was expected., -8615, 50
ACPL ERROR: A QUEUE keyword was expected., -8704, 72
ACPL ERROR: A REFERENCE parameter was expected., -8725, 77
ACPL ERROR: A string constant was expected., -8693, 68
ACPL ERROR: A table name was expected., -8543, 33
ACPL ERROR: A target attribute is not allowed., -8618, 51
Alphabetic Index
231
ACPL ERROR: A timer function must be an ACCELL/SQL function., -8707, 73

ACPL ERROR: A timer function name was expected., -8706, 73
ACPL ERROR: A TIMER keyword was expected., -8698, 70
ACPL ERROR: A user name was expected., -8558, 37
ACPL ERROR: A USERMENU keyword was expected., -8712, 74
ACPL ERROR: A variable was expected., -8560, 37
ACPL ERROR: ACCELL/SQL objects may not be used in a DDL command., -8765, 85
ACPL ERROR: An ACCELL/SQL statement was expected., -8567, 39
ACPL ERROR: An ACCELL/SQL type was expected., -8546, 34
ACPL ERROR: An application, form, schema, or table ID was expected., -8532, 31
ACPL ERROR: An array attribute was not expected., -8729, 78
ACPL ERROR: An attribute needs a variable name specified., -8583, 42
ACPL ERROR: An attribute was expected., -8568, 40
ACPL ERROR: An EVENT keyword was expected., -8699, 70
ACPL ERROR: An EVENTS keyword was expected., -8700, 71
ACPL ERROR: An expression was expected., -8590, 44
ACPL ERROR: An illegal character was ignored., -8566, 39
ACPL ERROR: Array dimensions were not expected., -8731, 79
ACPL ERROR: Array redefined., -8718, 76
ACPL ERROR: Array subscript was out of bounds., -8732, 79
ACPL ERROR: Bad timer function declaration., -8695, 69
ACPL ERROR: Call of a row-valued stored procedure in an expression., -8681, 65
ACPL ERROR: Cannot open file file_name., -8565, 39
ACPL ERROR: Clear to Add/Find expressions cannot be set using set/select., -8760, 84
ACPL ERROR: Clear to Add/Find expressions cannot be used in nested set statements., -8761, 84
ACPL ERROR: command_name: Command not defined., -8709, 74
ACPL ERROR: Could not change to the specified schema or database., -8657, 59
ACPL ERROR: Could not get database information., -8672, 63
ACPL ERROR: Could not open database., -8652, 58
ACPL ERROR: Database object name expected., -8740, 81
ACPL ERROR: Database privilege expected., -8739, 80
ACPL ERROR: Display location was expected., -8528, 31
ACPL ERROR: Display variables may not have code sections., -8651, 58
ACPL ERROR: Duplicate ACTION command attribute clause., -8684, 66
ACPL ERROR: Duplicate AUD_ACTION command attribute clause., -8685, 66
ACPL ERROR: Duplicate AUD_LABEL command attribute clause., -8688, 67
232
Alphabetic Index
ACPL ERROR: Duplicate button attribute clause., -8710, 74

ACPL ERROR: Duplicate command key(s) attribute clause., -8683, 65
ACPL ERROR: Duplicate FIND_ACTION command attribute clause., -8686, 66
ACPL ERROR: Duplicate FIND_LABEL command attribute clause., -8689, 67
ACPL ERROR: Duplicate LABEL command attribute clause., -8687, 67
ACPL ERROR: Either the 'KEY' or 'VALUES' keyword was expected., -8573, 40
ACPL ERROR: Error adding 'object_file', error number os_error., -8667, 62
ACPL ERROR: Error closing 'object_file', error number os_error., -8668, 62
ACPL ERROR: Error creating 'object_file', error number os_error., -8665, 62
ACPL ERROR: Error reading 'object_file', error number os_error., -8666, 62
ACPL ERROR: Exceeded maximum allowed nesting level., -8640, 56
ACPL ERROR: EXECUTING clause can only be used with a ROW_VALUED stored procedure., -8762, 85
ACPL ERROR: Fatal preprocessor error in 4GL script script_file., -8669, 63
ACPL ERROR: Illegal command action attribute value., -8694, 69
ACPL ERROR: Illegal command on non-updatable table or view., -8745, 82
ACPL ERROR: Invalid action specified for NEXT ACTION statement., -8658, 60
ACPL ERROR: Invalid array dimension type., -8719, 76
ACPL ERROR: Invalid array dimensions., -8730, 78
ACPL ERROR: Invalid array reference., -8733, 79
ACPL ERROR: Invalid array subscript., -8736, 80
ACPL ERROR: Invalid context for SELF., -8723, 77
ACPL ERROR: Invalid data type specified for RETRIEVE statement., -8751, 83
ACPL ERROR: Invalid function key number., -8645, 57
ACPL ERROR: Invalid mode specified., -8648, 58
ACPL ERROR: Invalid number of dimensions., -8721, 76
ACPL ERROR: Invalid SQL command., -8741, 81
ACPL ERROR: Invalid syntax for array attribute., -8728, 78
ACPL ERROR: Invalid timer function reference., -8697, 70
ACPL ERROR: Language section not valid in a Standard Form., -8599, 46
ACPL ERROR: Missing SQL statement terminator., -8743, 81
ACPL ERROR: Must use START TX in an application., -8634, 55
ACPL ERROR: No columns can be found., -8588, 44
ACPL ERROR: No command name was specified., -8692, 68
ACPL ERROR: No free registers, the expression is too complex., -8582, 42
ACPL ERROR: No FROM clause in SELECT statement., -8747, 83
ACPL ERROR: NULL or UNDEFINED expected., -8663, 61
Alphabetic Index
233
ACPL ERROR: NULLDATE token expected in compatibility mode only., -8664, 61

ACPL ERROR: Number of seconds for timer event was expected., -8701, 71
ACPL ERROR: Number of user functions exceeds maximum allowed., -8763, 85
ACPL ERROR: Object name is ambiguous - found in more than one schema., -8679, 65
ACPL ERROR: Old style database column name, remove '#'., -8759, 83
ACPL ERROR: Operation cannot be performed on this command., -8708, 73
ACPL ERROR: Programmable function keys are no longer supported., -8682, 65
ACPL ERROR: REF parameters cannot be passed to C-hooks or system functions., -8720, 76
ACPL ERROR: Statement can occur only in an ON FIELD code section., -8616, 50
ACPL ERROR: Statement can occur only in an ON FIND code section., -8619, 51
ACPL ERROR: Statement may not occur in a BEFORE APPLICATION code section., -8627, 53
ACPL ERROR: Statement may not occur in a BEFORE FORM code section., -8629, 53
ACPL ERROR: Statement may not occur in a WHEN FIELD CHANGES code section., -8628, 53
ACPL ERROR: Statement may not occur in an AFTER APPLICATION code section., -8626, 52
ACPL ERROR: Statement may not occur in an INIT FIELD code section., -8625, 52
ACPL ERROR: Statement may not occur in an ON FIND code section., -8624, 52
ACPL ERROR: Statement must be within an executing block., -8744, 82
ACPL ERROR: String constants exceeded the maximum number for a form., -8639, 56
ACPL ERROR: System Error., -8742, 81
ACPL ERROR: Table name not found in data dictionary., -8587, 43
ACPL ERROR: The '[' token was expected., -8714, 75
ACPL ERROR: The '[' token was unexpected., -8717, 76
ACPL ERROR: The ']' token was expected., -8716, 75
ACPL ERROR: The 'ACTION' keyword was expected., -8591, 44
ACPL ERROR: The 'ADD' or 'FIND' keyword was expected., -8593, 45
ACPL ERROR: The 'BEGIN' keyword was expected., -8512, 27
ACPL ERROR: The 'BY' keyword was expected., -8637, 55
ACPL ERROR: The 'CASE' or 'DEFAULT' keyword was expected., -8575, 41
ACPL ERROR: The 'CHANGES' keyword was expected., -8577, 41
ACPL ERROR: The 'END' keyword was expected., -8517, 28
ACPL ERROR: The 'FIELD' keyword was expected., -8518, 28
ACPL ERROR: The 'FILE' keyword was expected., -8750, 83
ACPL ERROR: The 'FIRST' keyword was expected., -8598, 46
ACPL ERROR: The 'FOR' keyword was expected., -8646, 57
ACPL ERROR: The 'FORM' keyword was expected., -8520, 28
ACPL ERROR: The 'FORMS' or 'FUNCTIONS' keyword was expected., -8738, 80
234
Alphabetic Index
ACPL ERROR: The 'FROM' keyword was expected., -8522, 29

ACPL ERROR: The 'FUNCTION' keyword was expected., -8523, 29
ACPL ERROR: The 'FUNCTIONS' keyword was expected., -8643, 57
ACPL ERROR: The 'IN' keyword was expected., -8529, 31
ACPL ERROR: The 'IS' keyword was expected., -8649, 58
ACPL ERROR: The 'LIST' or 'MATRIX' keyword was expected.
-8722, 77
-8735, 80
ACPL ERROR: The 'NEXT' keyword was expected., -8539, 32
ACPL ERROR: The 'ON' keyword was expected., -8644, 57
ACPL ERROR: The 'OPERATION' keyword was expected., -8620, 51
ACPL ERROR: The 'RECORD' keyword was expected., -8541, 33
ACPL ERROR: The 'RECORD' or 'FORM' keyword was expected., -8592, 45
ACPL ERROR: The 'RETURN' keyword was expected., -8641, 56
ACPL ERROR: The 'Screen' keyword was expected., -8633, 54
ACPL ERROR: The 'SELECT' keyword was expected., -8544, 34
ACPL ERROR: The 'SET' keyword was expected., -8545, 34
ACPL ERROR: The 'THEN' keyword was expected., -8550, 35
ACPL ERROR: The 'TO' keyword was expected.
-8553, 35
-8715, 75
ACPL ERROR: The 'TRIM' keyword was expected., -8554, 36
ACPL ERROR: The 'TX' keyword was expected., -8555, 36
ACPL ERROR: The 'UNTIL' keyword was expected., -8556, 36
ACPL ERROR: The 'USING' keyword was expected., -8557, 37
ACPL ERROR: The 'VALUES' keyword was expected., -8678, 64
ACPL ERROR: The 'ZOOM' keyword was expected., -8563, 38
ACPL ERROR: The CONSTANT expression was expected., -8600, 46
ACPL ERROR: The HANDLER keyword was expected., -8702, 71
ACPL ERROR: The keyword NULL is not permitted in this context., -8662, 61
ACPL ERROR: The number of set variables and selected columns do not match., -8746, 82
ACPL ERROR: The statement may not occur in current code section., -8632, 54
ACPL ERROR: The token WORK was expected., -8659, 60
ACPL ERROR: The variable list doesn't match # of scalar_db_exp's., -8595, 45
ACPL ERROR: There are too many program names (pipes) in the program list., -8631, 54
ACPL ERROR: There are too many symbol_type symbols., -8581, 42
ACPL ERROR: There is a bad function type., -8617, 50
ACPL ERROR: There is a bad master application variable., -8630, 54
Alphabetic Index
235
ACPL ERROR: There is a bad system variable., -8585, 43

ACPL ERROR: There is not enough memory., -8564, 38
ACPL ERROR: There was a bad conversion., -8580, 41
ACPL ERROR: There was a duplication of code section., -8635, 55
ACPL ERROR: There was an error in a control structure break call., -8611, 49
ACPL ERROR: There was an internal parser error., -8578, 41
ACPL ERROR: Timer functions must be global and declared in EXTERN statements., -8696, 69
ACPL ERROR: Too many characters in a single token., -8769, 85
ACPL ERROR: Too many errors, can't continue., -8584, 43
ACPL ERROR: Type can only be specified for a target variable., -8676, 64
ACPL ERROR: Type cannot be specified for an attribute., -8674, 64
ACPL ERROR: Type cannot be specified for an external variable., -8675, 64
ACPL ERROR: Type cannot be specified in a function's local clause., -8673, 63
ACPL ERROR: Type returned does not match function definition return type., -8772, 86
ACPL ERROR: Type specified does not match target column's type., -8677, 64
ACPL ERROR: Use of 'FROM' clause is valid only with 'DISPLAY HELP'., -8671, 63
All records in the selected set are locked by another user., -8864, 102
ALNK ERROR: ALNK : BAD Exit status = ., -8413, 21
ALNK ERROR: Could not find the '' form in the ' ' archive., -8418, 22
ALNK ERROR: Could not open or create the .al file., -8414, 21
ALNK ERROR: Error closing an application archive file, Status = ., -8409, 20
ALNK ERROR: Error opening application archive file ' ', Status = ., -8405, 18
ALNK ERROR: Form '' is not in the archive or the archive doesn't exist., -8404, 17
ALNK ERROR: Ran out of archive name space., -8411, 20
ALNK ERROR: Ran out of archive_names getting checksums., -8419, 22
ALNK ERROR: Ran out of memory while allocating archive index space., -8406, 19
ALNK ERROR: The application linker does not have enough memory., -8401, 16
ALNK ERROR: The specified master application form ' is not in archive ' '., -8408, 19
ALNK ERROR: There is a duplicate required form '' in the application., -8402, 16
ALNK ERROR: There was an error reading an archive index, Status = ., -8407, 19
ALNK ERROR: There was an error while closing the .al file, Status = ., -8415, 21
ALNK ERROR: There was an error while reading a form file, Status = ., -8410, 20
ALNK ERROR: There was an error while seeking or writing the .al file., -8416, 22
ALNK WARNING: Form could not be found in an archive., -8420, 22
An arithmetic overflow has occurred in a code section of the current form., -8810, 90
An arithmetic underflow has occurred in a code section of the current form., -8811, 90

An error has been generated from an RDBMS function., -9161, 159

An error occurred while activating the form., -9218, 165
An error occurred while closing a screen field help file., -9207, 164
An error occurred while closing internal form file: Field.frm, -9223, 167
An error occurred while closing the form., -9202, 163
An error occurred while linking a temporary file to the current file., -9143, 154
An error occurred while opening a SGLPNT temporary help file., -9237, 168
An error occurred while opening internal form file: Field.frm, -9221, 166
An error occurred while opening the form., -9200, 163
An error occurred while reading a SGLPNT temporary help file., -9238, 168
An error occurred while reading an existing screen field help file., -9208, 164
An error occurred while reading internal form file: Field.frm, -9222, 166
An error occurred while reading the form., -9201, 163
An error occurred while trying to delete the form file., -9138, 153
An error occurred while trying to link a screen field help file., -9217, 165
An error occurred while trying to open a screen field help file., -9206, 164
An error occurred while trying to open a window., -9175, 162
An error occurred while trying to open window: window_id., -9225, 167
An error occurred while trying to unlink a screen field help file., -9216, 165
An error occurred while trying to write a help file., -9141, 154
An error occurred while trying to write the backup form file., -9139, 154
An error occurred while trying to write the temporary form file., -9140, 154
An error occurred while writing a screen field help file., -9209, 164
An error occurred while writing a SGLPNT temporary help file., -9239, 169
An error was encountered writing to intermediate file 'file_name'., -10133, 185
An explicit column position was combined with the 'centered' keyword., -10158, 189
An expression or variable must be of type TEXT or BINARY., -9027, 140
An illegal function key number was encountered., -8974, 125
An illegal key string was assigned to a command's key attribute., -8973, 125
An integer constant was expected., -10206, 193
An internal database error has occurred., -11201, 201
An interrupt has occurred., -11311, 219
An invalid button location has been given., -8983, 128
An invalid character has been entered as a graphics character., -9120, 149
An invalid character has been entered., -9119, 149
An invalid display justification type was encountered., -8881, 105
Alphabetic Index
237
An invalid memory address was supplied as a parameter to an RHLI function., -11298, 217
An invalid regular expression was passed to reg_exp_str_compare$()., -8942, 117
An invalid scroll bar position has been entered., -9163, 159
An invalid stack address was encountered., -9015, 136
An invalid value has been entered., -9145, 155
An invalid variable or database type was detected., -8887, 106
An undefined ACCELL/SQL variable cannot be used in an SQL statement., -11250, 208
An unrecognized database error has occurred., -11200, 201
An X Window toolkit error occurred., -8967, 124
Array subscript out of bounds., -9000, 133
ASCEND or DESCEND are the only valid entries for this field., -9235, 168
Attempt to reference nonexistent row through use of a link., -11342, 226
Attempted an arithmetic operation with an old-style NULLDATE value., -8897, 107
Btree Manager Cannot open Database., -11216, 204

Bad arguments to 4GL system function., -8883, 105
Bad form location coordinates., -8976, 126
Bad heap size parameter: size., -8848, 98
Bad number of windows parameter: size., -8849, 98
Bad selection criteria., -11281, 214
Bad stack block size parameter: size., -8850, 98
Binding error., -11206, 202
Blanks cannot be used in array names. Please reenter an array name., -9270, 174
Blanks cannot be used in field names. Please reenter a field name., -9170, 161
Blanks cannot be used in file names. Please reenter the file name., -9171, 161
Blanks cannot be used in form names. Please reenter a form name., -9276, 176
Busymouse file read error., -8975, 126

Can't create a CREATE PIPELINE output file., -8877, 104
Can't initialize mode messages, see error file., -8950, 119
Cannot delete array with existing screen field references., -9269, 174
Cannot move farther down. The form is at the bottommost window edge., -9128, 151
Cannot move farther left. The form is at the leftmost window edge., -9125, 150
238
Alphabetic Index
Cannot move farther right. The form is at the rightmost window edge., -9126, 150
Cannot move farther up. The form is at the topmost window edge., -9127, 151
Cannot obtain information on a user., -8933, 115
Cannot open application database map file., -8936, 115
Cannot open the application '.al' map file., -8842, 96
Cannot read the application '.al' map file., -8843, 97
Cannot reference an undefined array., -9002, 133
Cannot switch to or obtain information on a schema., -8932, 114
Clear to add expressions are not supported for unbounded arrays., -9006, 134
CLEAR_FIND_EXP attribute's type does not match target field's type., -8954, 120
Close of text/binary data file failed., -11257, 210
Column not found in table., -11238, 207
Column type mismatch., -11282, 214
Combination group not allowed., -11286, 215
Command line access level must be between lower_limit and upper_limit., -8953, 119
Compile object does not match mapped object., -11278, 213
Configuration variable Bad format., -11295, 217
Configuration variable not found., -11296, 217
Conversion error., -11289, 215
Could not attach shared memory at required address., -11322, 221
Could not change to the specified schema or database., -9253, 171
Could not close database., -8914, 112
Could not close the database., -9248, 170
Could not commit a transaction., -8916, 113
Could not create a master application form., -9255, 172
-8958, 121
-9261, 173
-9316, 181
Could not open database - continuing without database information., -9317, 182
Could not open database., -8913, 112
Could not open the database., -9252, 171
Could not read the error message archive (SERRORS)., -8951, 119
Could not remove a file., -9256, 172
Cursor is at left edge of form. You cannot move any farther left., -9105, 146
Cursor is at right edge of form. You cannot move any farther right., -9106, 146
Data value conversion error., -11288, 215

Database has been modified., -11209, 202
Database interface internal error., -11213, 203
Alphabetic Index
239
Database is closed; attempt to access a database which is not open., -11291, 216
Date initialization failed., -8920, 113
Deadlock error, transaction rolled back., -11215, 204
DELETE cannot be used in the middle of a field., -9134, 152
Denied access to file., -11299, 217
Duplicate key found in No duplicate Btree., -11294, 216
Duplicate Row ids found., -11222, 204
Either 'desc' or a named expression was expected., -10214, 195

-11297, 217
-11307, 218
Entire text field must be within, or outside of the repeating area., -9278, 176
Error accessing network., -11214, 203
Error closing file: ., -9304, 179
Error creating file: ., -9305, 179
Error in WRITE PIPELINE statement. Check operation of pipe programs., -8905, 109
Error initializing ACCELL/SQL environment: ., -8945, 118
Error opening Btree., -11285, 215
Error opening file: ., -9301, 178
Error reading file: ., -9302, 178
Error writing file: ., -9303, 178

Failed to close a file., -11300, 217
Fatal error in Btree access; rebuild,, -11284, 214
Field array cell subscript out of bounds: ., -9322, 183
Field cannot be moved here because it will overlap an existing field., -9135, 153
Field name from this table already used as a screen field or array., -9277, 176
FIELD_CLASS statement for an undefined array: ., -9323, 183
File create error., -11301, 218
File descriptor not mapped., -11348, 228
File does not exist., -11333, 224
file open error:, -9726, 184
File seek error., -11303, 218

Find count must be greater than or equal to 0., -9281, 177

Fixed trim cannot be marked within non-repeating trim., -9158, 158
Form is at bottom edge of window. It cannot be moved down any more., -9112, 147
Form is at left edge of window. It cannot be moved left any more., -9109, 146
Form is at right edge of window. It cannot be moved right any more., -9110, 147
Form is at top edge of window. It cannot be moved up any more., -9111, 147
Form's bottom border cannot be moved up any more due to existing trim., -9130, 152
Form's left border cannot be moved left any more due to existing trim., -9129, 151
frminit: Error from wnopen., -9231, 167
Generic operating system error., -11293, 216

Illegal argument., -11308, 219
Illegal command action specifier string., -8971, 124
Illegal form cache size: size., -9013, 136
Illegal global function cache size: size., -9014, 136
Illegal initial memory size: size., -8946, 118
Illegal label action specifier string., -8972, 124
Illegal maximum number of open variable length data files: number., -9021, 138
Illegal maximum sort memory size: size., -8947, 118
Illegal number of open archives archive_number., -8952, 119
Illegal reference of an unusable view., -11207, 202
Illegal selected set directory name: directory_name., -8948, 118
Illegal test for value type., -11309, 219
Illegal timer function argument., -8979, 126
Illegal transaction ID., -11310, 219
Illegal use of variable 'variable_name'., -10163, 191
Illegal variable length data file directory name: directory_search_path., -9020, 138
Illegal variable length data in-memory limit: length., -9019, 138
Implicit conversion error., -11225, 205
Indeterminate error while reading target table information., -9315, 181
Indeterminate window manager error., -9314, 181
Input column table.column_name does not have its type specified, and it is not a database column., -10161, 190
Alphabetic Index
241
Insufficient heap memory to display text in field., -9033, 141

Insufficient heap memory to edit text in field. Use system editor., -9034, 141
Insufficient heap size to edit the current text line. Adjust heap size., -9036, 142
Insufficient memory available., -9709, 184
Insufficient memory for argument list., -10137, 186
Internal cache manager error (nonfatal)., -11287, 215
Internal error accessing ASQLCRSR pool., -11240, 207
Internal error accessing ASQLINFO pool., -11241, 207
Internal error while opening a window., -9245, 170
Internal error while sizing form., -9244, 169
Internal error, ACCELL/SQL type not supported by database., -11249, 208
Internal error, invalid SQLID., -11247, 208
Internal error, unknown signal., -11253, 209
Internal error, unsupported database type., -11251, 209
Internal error: Unexpected command type number in docom., -10145, 188
Internal error: Unexpected type in comptyp type., -10171, 192
Internal error: Unrecognized style in settyp., -10176, 192
Internal problem with null values., -8930, 113
Invalid arguments specified with this command., -8986, 129
Invalid array class. Array classes are Matrix and List., -9267, 174
Invalid array dimensions., -9004, 134
Invalid array subscript., -9011, 136
Invalid array subscript, missing right bracket., -9012, 136
Invalid attribute, a list array cannot reference a matrix attribute., -9009, 135
Invalid attribute, a matrix array cannot reference a list attribute., -9010, 135
Invalid attribute, a scalar cannot reference an array attribute., -9008, 135
Invalid break point was specified., -8993, 131
Invalid case conversion type has been entered., -9174, 162
Invalid column ID/not part of common table., -11323, 222
Invalid column number column_number generated by print statement on line line_number., -10134, 186
Invalid command from a file., -8996, 131
Invalid current line no., -8995, 131
Invalid debugger command was specified., -8999, 132
Invalid debugger license., -8994, 131
Invalid default justification., -8894, 106
Invalid default type., -11313, 220
242
Alphabetic Index
Invalid error number., -9701, 184

Invalid field attribute was specified., -8991, 130
Invalid field name was specified., -8985, 129
Invalid file name was specified., -8998, 132
Invalid form attribute or field name was specified., -8990, 130
Invalid form name was specified., -8992, 130
Invalid justification type. Please reenter the justify type., -9149, 156
Invalid line number was specified., -8984, 129
Invalid name (Name not supplied or name contains reserved characters., -11279, 213
Invalid number of zoom values returned., -8960, 121
Invalid Presentation Mode specified for the ACCELL/SQL Debugger., -8997, 131
Invalid screen field name., -9274, 175
Invalid setting of ACLPRESMODE configuration variable., -8970, 124
Invalid table ID., -11347, 228
Invalid transaction token., -9310, 180
Invalid type for array subscript., -9001, 133
Invalid Username/Password., -8959, 121
Invalid value for $info_level. Setting $info_level to 1 (intermediate)., -9040, 143
Invalid value for this statement., -8957, 121
Invalid value specified for a screen field's COL attribute., -9041, 143
Invalid value specified for a screen field's ROW attribute., -9042, 144
Invalid value was specified for WINDOW_HEIGHT field attribute., -9028, 140
Invalid value was specified., -8988, 130
Key already exists in hash table., -11344, 226

Key column(s) required., -11335, 224
Key not found., -11317, 220

Last operation required more heap than available. Last edit lost., -9035, 141
Lock granted due to upper level lock., -11304, 218
Lock Manager initialization failure., -11316, 220
Log file does not exist., -11337, 225

Mapping of C-hook functions failed when opening the database., -8940, 116
Missing parameter to a stored procedure., -11219, 204

243
No current row for 'column type' default., -11326, 222

No current row for CROW type default., -11325, 222
No default for this column., -11330, 223
No more characters can be inserted. The current line is full., -9104, 146
No privilege for the attempted operation., -11340, 225
No space in db for some resource., -11204, 202
No space left on device., -11346, 227
No such file, directory, or program., -11332, 224
No target table has been specified for this form., -9167, 160
Not a column group., -11324, 222
Not all fields can be accommodated in the default form., -9263, 173
Not all required fields have been entered - ADD REJECTED., -8939, 116
Not enough memory on the heap to write the form., -9213, 165
Not enough shared memory; try increasing 'SHMMAX' or decreasing 'SHMFULL'., -11345, 227
Null values are not supported in the underlying database., -8943, 117

Object does not exist., -11339, 225
Object name is ambiguous or multiply defined., -11237, 207
Only a start transaction is allowed from an application form., -9177, 163
Only the characters 'T' or ' ' (space) can be used on this form., -9156, 158
Open/create of text/binary data file failed., -11256, 210
Operand type clash., -11226, 205
Operating system interrupt handler problem., -8921, 113
Operation is invalid in middle of a multi-line text field., -9273, 175
Operation not allowed., -9018, 137
Operator not found., -10260, 197
Out of heap memory., -11254, 209
Out of memory.
-11255, 209
-9300, 178
Output width overflow from function 'function_name'., -10250, 197

Partial success; see the individual status list., -11302, 218
Privilege does not exist., -11341, 226
Process terminated at user request (typically using 'shutdb' utility)., -11315, 220
244
Alphabetic Index
Queued command execution failed., -8981, 127

Queued command not enabled in current mode., -8982, 128

Read of text/binary data file failed., -11258, 211
Record number is outside of the current selected set., -8956, 120
Request was not a demotion request., -11329, 223
Row does not have read permission., -11312, 219
Row does not have write permission., -11343, 226

SAR ERROR: Error adding 'file_name', error number error#., -8209, 4
SAR ERROR: Error reading 'file_name', error number error#., -8208, 4
SAR ERROR: Error renaming 'file_name' to 'file_name'., -8210, 5
SAR ERROR: Cannot close 'archive_name', error number os_error., -8207, 4
SAR ERROR: Cannot create 'archive_name', error number os_error., -8206, 4
SAR ERROR: Cannot open 'archive_name', error number os_error., -8205, 3
SAR ERROR: There is a corrupt archive file archive_name., -8201, 3
Scan (or ordered access) ID is not found (Has scan been closed?)., -11280, 214
Selection table full., -11321, 221
Some command definitions are missing from the unicap file., -8857, 100
Sort/merge file open/creation failed., -11290, 216
Subscript is missing from array reference, value is undefined., -9003, 134
System log is full., -11223, 205

Target field names cannot be used for array names., -9272, 175
Test requires a value., -11349, 228
The ACCELL/SQL help sub-system file cannot be found or is not readable., -8829, 94
The binary data type cannot be used for form screen fields., -9275, 176
The CLEAR TO FIND command requires at least one searchable field., -8903, 109
The column cannot be changed due to references to it., -11314, 220
Alphabetic Index
245
The column data type internal length is larger than the maximum length., -11292, 216
The command entered is invalid in the current mode., -8898, 108
The command just entered is not recognized., -9137, 153
The create on intermediate file '' failed., -10131, 185
The create on tag file '' failed., -10132, 185
The current field is required., -8899, 108
The current form is read only, insert/update/delete not allowed., -9017, 137
The current operation requires more heap memory than available., -8813, 91
The current record cannot be deleted., -8841, 96
The current record could not be locked. Try again later., -8859, 101
The cursor cannot move down any more., -9117, 148
The cursor cannot move left any more., -9114, 148
The cursor cannot move right any more., -9115, 148
The cursor cannot move up any more., -9116, 148
The data type being returned does not match the function definition., -9046, 144
The data type in the C-hook return value is invalid., -8966, 123
The data types for this operation do not match., -8815, 91
The database design is different from when the application was created., -8855, 100
The database has been changed. Use EXPLAIN ERROR for more information., -9172, 161
The database root volume (i.e. 'file.db') cannot be accessed., -11327, 223
The field cannot be moved here because it will overlap existing trim., -9136, 153
The file is not in the proper format., -8802, 87
The file name is too long. File names are limited to 14 characters., -9173, 161
The form cannot be displayed at the specified location., -8808, 89
The form is too large for the terminal screen., -9280, 177
The form must be made larger before additional trim can be added., -9155, 157
The form name specified in an ERASE TRIM statement has not been displayed., -8865, 102
The form referenced in the code section is not active., -8826, 93
The function key specified is not known to this form., -8922, 113
The Generator has run out of memory., -9243, 169
The help form archive file cannot be found., -8818, 92
The help form cannot be found in the help archive file., -8819, 93
The if clause on line does not contain an integer expression., -10159, 189
The input line buffer is too small., -10135, 186
-11276, 213
-8938, 115

The input value is not within the valid field range., -9100, 145
The internal_table_name table has overflowed., -10230, 196
The justification specifier is invalid., -8840, 96
The keyword NULL appears in an invalid ACCELL/4GL context., -8931, 114
The main help form is not in the help sub-system description file., -8858, 101
The number of columns returned does not match the number expected., -11248, 208
The only valid entries for this field are - Yes or No., -9147, 155
The open on tag file 'file_name' failed., -10141, 187
The parameter types for an ACCELL/SQL function call do not match., -9007, 135
The pipeline variable for a pipe must be of type NUMERIC., -8876, 103
The record has changed since the last read., -8961, 122
The record you are attempting to position on has an undefined row id., -9037, 142
The record you are attempting to position on has been deleted., -8963, 123
The record you are attempting to read has an undefined row id., -9038, 143
The record you are attempting to update or delete has been deleted., -8962, 122
The referenced ACCELL/SQL help file cannot be found or is not readable., -8828, 93
The referenced C-hook function cannot be found., -8847, 98
The referenced form is unknown to the Manager., -8854, 99
The referenced help form cannot be found in the help description file., -8831, 94
The referenced help form has too many 'next forms' associated with it., -8830, 94
The referenced identifier does not refer to a form., -9016, 137
The referenced variable does not refer to a screen field., -8860, 101
The referenced variable is not a target variable., -8861, 101
The requested command is inactive in current mode., -9157, 158
The resultant string has overflowed the display format., -8937, 115
The row was NOT deleted., -11328, 223
The screen field is not wide enough for the formatted value., -8895, 107
The screen field length is longer than the target field length., -9176, 162
The software version does not match the shared memory segment version., -11334, 224
The software version does not match the shared memory version., -11338, 225
The specified database table name cannot be found in the database., -9160, 158
The specified field name cannot be found in the target table., -9166, 160
The specified file cannot be found., -8814, 91
The specified form cannot be found in the form archive., -8809, 89
The specified help form could not be found in the specified help archive., -8955, 120
The specified input length is too long. Please reenter a new value., -9151, 157
Alphabetic Index
247
The specified search criteria is invalid., -8839, 96

The specified value is not in correct AMOUNT format., -8912, 111
The specified value is not in correct BOOLEAN format., -8909, 110
The specified value is not in correct FLOAT format., -8910, 111
The specified value is not in correct NUMERIC format., -8911, 111
The specified value is not in correct TIME format., -8908, 110
The specified value is not in the correct DATE format., -8812, 90
The unicap file could not be opened., -8844, 97
The UNIFY configuration variable is not set., -9254, 172
The value of variable 'variable_name' is never set., -10173, 192
The value's data type is incorrect for this operation., -8816, 92
The width has been set to a value less than or equal to the left margin., -10174, 192
The write to FNDFLD failed -- error_message., -10265, 198
There are no errors to report., -8800, 87
There are no input records., -10140, 187
There are no options on that menu., -10763, 199
There are no records in the selected set., -8834, 95
There are too many active windows., -8807, 89
There are too many saved strings., -10144, 188
There has been an abnormal pipeline program termination., -8879, 104
There has been an I/O error detected by the system., -8806, 88
There has been an internal system error., -8803, 88
There is a nested aggregate operator on line line_number., -10165, 191
There is a phase error in the input file., -10136, 186
There is a saved string overflow., -10143, 188
There is a type mismatch in the set statement on line line_number. The variable type is type1 and the expression
type is type2., -10164, 191
There is a variable used in a sort expression on line line_number., -10169, 191
There is an aggregate expression embedded in a sort expression on line line_number., -10167, 191
There is an assignment to a non-variable on line line_number., -10151, 189
There is an error in an 'if' expression., -10213, 195
There is an integer constant expected for the length., -10211, 194
There is an invalid 'in column' clause., -10216, 195
There is an invalid 'using' clause., -10217, 195
There is an invalid aggregate expression., -10218, 196
There is an invalid function argument list., -10219, 196
There is an invalid input item., -10209, 194
248
Alphabetic Index
There is an invalid non-section statement., -10205, 193

There is an invalid print item., -10215, 195
There is an invalid statement., -10212, 194
There is an invalid type expression., -10210, 194
There is an undefined boolean variable in a statement., -8902, 109
There is insufficient memory for output line buffer., -10138, 187
There is insufficient memory for the input columns., -10162, 190
There is insufficient memory to hold variables., -10139, 187
There is insufficient memory to store the constants., -10231, 197
There is no 'next form' for this form., -8845, 97
There is no active form., -8989, 130
There is no trim to delete., -9101, 145
There is not enough memory to activate the form., -8801, 87
There is not enough memory to continue processing., -8804, 88
There is not enough memory to grow an unbounded array., -9005, 134
There isn't enough room on the form to insert a new line., -9103, 145
There was a bad type involved in conversion., -8907, 110
There was an error initializing the keyboard information., -9219, 166
There was an error initializing the window manager., -9220, 166
There was an error while reading/accessing a variable length data file., -9024, 139
There was an error while writing to a variable length data file., -9025, 139
There was an output width overflow from the print expression on line number line_number., -10142, 188
This array cell is already referenced by another field on this form., -9268, 174
This array name is already used for a field on this form., -9271, 174
This array name is already used for another array on this form., -9265, 173
This field name is already used as a sort field., -9279, 176
This field name is already used for another field on this form., -9153, 157
This is the first record., -8836, 95
This is the first set., -8838, 95
This is the last record., -8835, 95
This is the last set., -8837, 95
This isn't a valid edit mode. Edit modes are Replace or Insert., -9154, 157
This isn't a valid field data type. Please reenter the data type., -9148, 155
This isn't a valid order entry. Ordering can be by Row or Column only., -9162, 159
Timer event creation failed., -8980, 127
'TO' keyword missing on the command line., -8987, 129
Alphabetic Index
249
Too many or no pipeline tasks have been started., -8880, 105

Too many scans (and/or ordered accesses) active at once., -11320, 221
Transaction aborted by SQL Server, -11260, 212
Transaction has no locks., -11270, 212
Transaction levels can only be within the range of 1-5., -9169, 160
Transaction logging has not been enabled - transactions cannot be aborted., -11331, 223
Transaction logging not turned on., -11318, 221
Trim cannot be inserted while on a screen field., -9132, 152
Trim cannot be placed on top of an existing field., -9123, 150
Trim does not exist., -8866, 102
Type conversion error. Left type is type1, right type is type2, operator is operator., -10150, 189
Unable to back out operation - fatal., -11283, 214

Unable to change array class from Matrix to List., -9266, 173
Unable to execute FNDFLD -- error_message., -10264, 198
Unable to execute the sort command., -10146, 188
Unable to execute the system editor., -9247, 170
Unable to find default schema, 'syncauth' may need to be run., -10788, 199
Unable to find help documentation for this selection., -10767, 199
Unable to find menu/program by that name., -10812, 200
Unable to open input file 'file_name'., -10181, 193
Unable to open script file 'file_name'., -10220, 196
Unable to open the Generator's temporary file., -9242, 169
Unable to validate licensing information., -8965, 123
Unexpected End-Of-File encountered., -9312, 180
Unexpected field input length specification encountered., -9324, 183
Unexpected field window height specification encountered., -9325, 184
Unexpected token encountered: token_string., -9313, 181
Unexpected type in intsize number., -10263, 197
Unknown or invalid value in switch., -9710, 184
Unknown string expression type., -10261, 197
Unrecognized character: 'character'., -10204, 193
Unrecognized type in set statement. Expression type type1, variable type type2., -10160, 190
Unreplace cannot be used while the cursor is on a screen field., -9121, 149
Unreplace commands can only be used while in replace mode., -9113, 147
250
Alphabetic Index
Use the DELETE FIELD command to remove a screen field., -9133, 152
User benign rollback., -11232, 207
User defined error for rollback., -11230, 206
User defined error.
-11228, 205
-11229, 206
User has improper permission to access the file., -8805, 88
Valid, but no work was done., -11211, 203

Value is undefined., -8886, 106

Warning - Invalid ACCELL/SQL TYPE specified: data_type., -9311, 180
Warning - Invalid target table name given., -9308, 179
Warning - No target table name given., -9307, 179
WARNING! Target table and field information has been cleared., -9260, 172
Warning, 'column_name' was not a target column in the target table, but is now., -9320, 183
Warning, column_name was a column in the target table, but is not now., -9309, 180
Warning, length for column 'column_name' changed in database, length being changed for target variable.,
-9319, 182
Warning, old rhli type encountered for 'column_name', ascii file needs to be upgraded., -9321, 183
Warning, type for column 'column_name' changed in database, type being changed for target variable., -9318,
182
Write of text/binary data file failed., -11259, 211
Wrong number of arguments in an ACCELL/SQL function call., -8906, 110
Wrong number of columns returned from a stored procedure., -11218, 204
Alphabetic Index
251
252
Alphabetic Index
Numerical Index
Use this index to find messages in numeric order by message number. The message
number is presented first, followed by the message text and the page where the message
is described, as shown in this example:
-8862, A subtraction operation was attempted on a string value., 118
Message
number
Message
text
Page
number
-10131, The create on intermediate file 'file_name' failed., 185

-10132, The create on tag file 'file_name' failed., 185
-10133, An error was encountered writing to intermediate file 'file_name'., 185
-10134, Invalid column number column_number generated by print statement on line line_number., 186
-10135, The input line buffer is too small., 186
-10136, There is a phase error in the input file., 186
-10137, Insufficient memory for argument list., 186
-10138, There is insufficient memory for output line buffer., 187
-10139, There is insufficient memory to hold variables., 187
-10140, There are no input records., 187
-10141, The open on tag file 'file_name' failed., 187
-10142, There was an output width overflow from the print expression on line number line_number., 188
-10143, There is a saved string overflow., 188
-10144, There are too many saved strings., 188
-10145, Internal error: Unexpected command type number in docom., 188
-10146, Unable to execute the sort command., 188
-10150, Type conversion error. Left type is type1, right type is type2, operator is operator., 189
-10151, There is an assignment to a non-variable on line line_number., 189
-10152, 'Name' in the section header on line line_number is not an existing sort expression., 189
-10158, An explicit column position was combined with the 'centered' keyword., 189
-10159, The if clause on line line_number does not contain an integer expression., 189
-10160, Unrecognized type in set statement. Expression type type1, variable type type2., 190
253
-10161, Input column table.column_name does not have its type specified, and it is not a database column., 190
-10162, There is insufficient memory for the input columns., 190
-10163, Illegal use of variable 'variable_name'., 191
-10164, There is a type mismatch in the set statement on line line_number. The variable type is type1 and the
expression type is type2., 191
-10165, There is a nested aggregate operator on line line_number., 191
-10167, There is an aggregate expression embedded in a sort expression on line line_number., 191
-10169, There is a variable used in a sort expression on line line_number., 191
-10170, 'Function_name' is an unrecognized function name., 192
-10171, Internal error: Unexpected type in comptyp type., 192
-10173, The value of variable 'variable_name' is never set., 192
-10174, The width has been set to a value less than or equal to the left margin., 192
-10176, Internal error: Unrecognized style in settyp., 192
-10181, Unable to open input file 'file_name'., 193
-10204, Unrecognized character: 'character'., 193
-10205, There is an invalid non-section statement., 193
-10206, An integer constant was expected., 193
-10207, A sort command is not allowed on presorted input., 193
-10208, A string constant was expected., 194
-10209, There is an invalid input item., 194
-10210, There is an invalid type expression., 194
-10211, There is an integer constant expected for the length., 194
-10212, There is an invalid statement., 194
-10213, There is an error in an 'if' expression., 195
-10214, Either 'desc' or a named expression was expected., 195
-10215, There is an invalid print item., 195
-10216, There is an invalid 'in column' clause., 195
-10217, There is an invalid 'using' clause., 195
-10218, There is an invalid aggregate expression., 196
-10219, There is an invalid function argument list., 196
-10220, Unable to open script file 'file_name'., 196
-10230, The internal_table_name table has overflowed., 196
-10231, There is insufficient memory to store the constants., 197
-10250, Output width overflow from function 'function_name'., 197
-10260, Operator not found., 197
-10261, Unknown string expression type., 197
-10263, Unexpected type in intsize number., 197
254
Numeric Index
-10264, Unable to execute FNDFLD -- error_message., 198

-10265, The write to FNDFLD failed -- error_message., 198
-10763, There are no options on that menu., 199
-10767, Unable to find help documentation for this selection., 199
-10788, Unable to find default schema, 'syncauth' may need to be run., 199
-10812, Unable to find menu/program by that name., 200
-11200, An unrecognized database error has occurred., 201
-11201, An internal database error has occurred., 201
-11204, No space in db for some resource., 202
-11206, Binding error., 202
-11207, Illegal reference of an unusable view., 202
-11209, Database has been modified., 202
-11211, Valid, but no work was done., 203
-11213, Database interface internal error., 203
-11214, Error accessing network., 203
-11215, Deadlock error, transaction rolled back., 204
-11216, Btree Manager Cannot open Database., 204
-11218, Wrong number of columns returned from a stored procedure., 204
-11219, Missing parameter to a stored procedure., 204
-11222, Duplicate Row ids found., 204
-11223, System log is full., 205
-11225, Implicit conversion error., 205
-11226, Operand type clash., 205
-11227, A column insert or update conflicts with a rule., 205
-11228, User defined error., 205
-11229, User defined error., 206
-11230, User defined error for rollback., 206
-11232, User benign rollback., 207
-11237, Object name is ambiguous or multiply defined., 207
-11238, Column not found in table., 207
-11240, Internal error accessing ASQLCRSR pool., 207
-11241, Internal error accessing ASQLINFO pool., 207
-11242, Internal error, invalid SQLID., 208
-11248, The number of columns returned does not match the number expected., 208
-11249, Internal error, ACCELL/SQL type not supported by database., 208
-11250, An undefined ACCELL/SQL variable cannot be used in an SQL statement., 208
Numeric Index
255
-11251, Internal error, unsupported database type., 209

-11253, Internal error, unknown signal., 209
-11254, Out of heap memory., 209
-11255, Out of memory., 209
-11256, Open/create of text/binary data file failed., 210
-11257, Close of text/binary data file failed., 210
-11258, Read of text/binary data file failed., 211
-11259, Write of text/binary data file failed., 211
-11260, Transaction aborted by SQL Server, 212
-11270, Transaction has no locks., 212
-11275, A null value was specified for a column with the 'notnull' attribute., 213
-11276, The input string is invalid for the given data type., 213
-11278, Compile object does not match mapped object., 213
-11279, Invalid name (Name not supplied or name contains reserved characters., 213
-11280, Scan (or ordered access) ID is not found (Has scan been closed?)., 214
-11281, Bad selection criteria., 214
-11282, Column type mismatch., 214
-11283, Unable to back out operation - fatal., 214
-11284, Fatal error in Btree access; rebuild,, 214
-11285, Error opening Btree., 215
-11286, Combination group not allowed., 215
-11287, Internal cache manager error (nonfatal)., 215
-11288, Data value conversion error., 215
-11289, Conversion error., 215
-11290, Sort/merge file open/creation failed., 216
-11291, Database is closed; attempt to access a database which is not open., 216
-11292, The column data type internal length is larger than the maximum length., 216
-11293, Generic operating system error., 216
-11294, Duplicate key found in No duplicate Btree., 216
-11295, Configuration variable Bad format., 217
-11296, Configuration variable not found., 217
-11297, End of scan (or ordered access)., 217
-11298, An invalid memory address was supplied as a parameter to an RHLI function., 217
-11299, Denied access to file., 217
-11300, Failed to close a file., 217
-11301, File create error., 218

-11302, Partial success; see the individual status list., 218

-11303, File seek error., 218
-11304, Lock granted due to upper level lock., 218
-11307, End of scan (or ordered access)., 218
-11308, Illegal argument., 219
-11309, Illegal test for value type., 219
-11310, Illegal transaction ID., 219
-11311, An interrupt has occurred., 219
-11312, Row does not have read permission., 219
-11313, Invalid default type., 220
-11314, The column cannot be changed due to references to it., 220
-11315, Process terminated at user request (typically using 'shutdb' utility)., 220
-11316, Lock Manager initialization failure., 220
-11317, Key not found., 220
-11318, Transaction logging not turned on., 221
-11320, Too many scans (and/or ordered accesses) active at once., 221
-11321, Selection table full., 221
-11322, Could not attach shared memory at required address., 221
-11323, Invalid column ID/not part of common table., 222
-11324, Not a column group., 222
-11325, No current row for CROW type default., 222
-11326, No current row for 'column type' default., 222
-11327, The database root volume (i.e. 'file.db') cannot be accessed., 223
-11328, The row was NOT deleted., 223
-11329, Request was not a demotion request., 223
-11330, No default for this column., 223
-11331, Transaction logging has not been enabled - transactions cannot be aborted., 223
-11332, No such file, directory, or program., 224
-11333, File does not exist., 224
-11334, The software version does not match the shared memory segment version., 224
-11335, Key column(s) required., 224
-11337, Log file does not exist., 225
-11338, The software version does not match the shared memory version., 225
-11339, Object does not exist., 225
-11340, No privilege for the attempted operation., 225
-11341, Privilege does not exist., 226

257
-11342, Attempt to reference nonexistent row through use of a link., 226

-11343, Row does not have write permission., 226
-11344, Key already exists in hash table., 226
-11345, Not enough shared memory; try increasing 'SHMMAX' or decreasing 'SHMFULL'., 227
-11346, No space left on device., 227
-11347, Invalid table ID., 228
-11348, File descriptor not mapped., 228
-11349, Test requires a value., 228
-8201, SAR ERROR: There is a corrupt archive file archive_name., 3
-8205, SAR ERROR: Cannot open 'archive_name', error number os_error., 3
-8206, SAR ERROR: Cannot create 'archive_name', error number os_error., 4
-8207, SAR ERROR: Cannot close 'archive_name', error number os_error., 4
-8208, SAR ERROR: Error reading 'file_name', error number error#., 4
-8209, SAR ERROR: Error adding 'file_name', error number error#., 4
-8210, SAR ERROR: Error renaming 'file_name' to 'file_name'., 5
-8300, ACMB ERROR: There was an error in reading the file file_name., 5
-8301, ACMB ERROR: There was a bad magic number., 6
-8302, ACMB ERROR: The Combine failed in malloc memory., 6
-8303, ACMB ERROR: Couldn't find a 'next field'., 7
-8304, ACMB ERROR: Checksum error. Verify .fs and .fq target table names match., 7
-8305, ACMB ERROR: The field field_name is not in the file file_name.[af]q., 8
-8306, ACMB ERROR: There was a form name mismatch., 8
-8307, ACMB ERROR: There was a form/application mismatch., 9
-8308, ACMB ERROR: There is a corrupt file., 9
-8309, ACMB ERROR: There was an error in adding the form., 9
-8310, ACMB ERROR: The form name has multiple definitions., 10
-8311, ACMB ERROR: There was an error in reading the form., 11
-8312, ACMB ERROR: Warning: there was an illegal display variable name: variable_name., 11
-8313, ACMB ERROR: There was an error opening 'file_name', error number os_error., 11
-8314, ACMB ERROR: There was an error renaming 'temp_archive_name' to 'existing_archive_name'., 12
-8315, ACMB ERROR: There was an error creating 'file_name', error number os_error., 12
-8316, ACMB ERROR: There was an error closing a file, error number os_error., 13
-8317, ACMB ERROR: Type conflict on target variable variable_name., 13
-8318, ACMB ERROR: The DBTYPE configuration variable is not set or is set incorrectly., 13
-8319, ACMB ERROR: 'table_name' used as target table in 4GL, no target table declared in generator., 13
-8320, ACMB ERROR: 'table_name' used as target table in AGEN, no target table in 4GL., 14
258
Numeric Index
-8321, ACMB ERROR: 'table_name' used as target table in AGEN, table_name used as target table in 4GL.,
14
-8322, ACMB ERROR: Number of target columns known to .fq and .fo for table 'table_name' do not match.,
14
-8323, ACMB ERROR: Columns in target table 'table_name' for .fq and .fo differ., 14
-8324, ACMB ERROR: The characteristics of column 'column_name' are different in the .fq and .fo., 15
-8325, ACMB ERROR: There was a class mismatch for field 'field_name'., 15
-8326, ACMB ERROR: The local array 'array_name' was not defined., 15
-8401, ALNK ERROR: The application linker does not have enough memory., 16
-8402, ALNK ERROR: There is a duplicate required form 'form_name' in the application., 16
-8404, ALNK ERROR: Form 'form_name' is not in the archive or the archive doesn't exist., 17
-8405, ALNK ERROR: Error opening application archive file 'archive_name', Status = status_value., 18
-8406, ALNK ERROR: Ran out of memory while allocating archive index space., 19
-8407, ALNK ERROR: There was an error reading an archive index, Status = os_error., 19
-8408, ALNK ERROR: The specified master application form 'form_name is not in archive 'archive_name'., 19
-8409, ALNK ERROR: Error closing an application archive file, Status = os_error., 20
-8410, ALNK ERROR: There was an error while reading a form file, Status = status_value., 20
-8411, ALNK ERROR: Ran out of archive name space., 20
-8413, ALNK ERROR: ALNK : BAD Exit status = error_number., 21
-8414, ALNK ERROR: Could not open or create the .al file., 21
-8415, ALNK ERROR: There was an error while closing the .al file, Status = os_error., 21
-8416, ALNK ERROR: There was an error while seeking or writing the .al file., 22
-8418, ALNK ERROR: Could not find the 'form_name' form in the 'archive_name' archive., 22
-8419, ALNK ERROR: Ran out of archive_names getting checksums., 22
-8420, ALNK WARNING: Form form_name could not be found in an archive., 22
-8501, ACPL ERROR: A "(" operator was expected., 24
-8502, ACPL ERROR: A ")" operator was expected., 24
-8503, ACPL ERROR: A "," was expected., 25
-8504, ACPL ERROR: A form or function name exceeded 15 characters in length., 26
-8505, ACPL ERROR: A ":" was expected., 26
-8506, ACPL ERROR: A ";" was expected., 27
-8512, ACPL ERROR: The 'BEGIN' keyword was expected., 27
-8517, ACPL ERROR: The 'END' keyword was expected., 28
-8518, ACPL ERROR: The 'FIELD' keyword was expected., 28
-8520, ACPL ERROR: The 'FORM' keyword was expected., 28
-8522, ACPL ERROR: The 'FROM' keyword was expected., 29
-8523, ACPL ERROR: The 'FUNCTION' keyword was expected., 29
Numeric Index
259
-8524, ACPL ERROR: A field ID was expected., 29

-8525, ACPL ERROR: A file ID was expected., 30
-8526, ACPL ERROR: A form ID was expected., 30
-8527, ACPL ERROR: A form, application or user function definition was expected., 30
-8528, ACPL ERROR: Display location was expected., 31
-8529, ACPL ERROR: The 'IN' keyword was expected., 31
-8532, ACPL ERROR: An application, form, schema, or table ID was expected., 31
-8533, ACPL ERROR: A justification specification was expected., 32
-8539, ACPL ERROR: The 'NEXT' keyword was expected., 32
-8541, ACPL ERROR: The 'RECORD' keyword was expected., 33
-8543, ACPL ERROR: A table name was expected., 33
-8544, ACPL ERROR: The 'SELECT' keyword was expected., 34
-8545, ACPL ERROR: The 'SET' keyword was expected., 34
-8546, ACPL ERROR: An ACCELL/SQL type was expected., 34
-8550, ACPL ERROR: The 'THEN' keyword was expected., 35
-8553, ACPL ERROR: The 'TO' keyword was expected., 35
-8554, ACPL ERROR: The 'TRIM' keyword was expected., 36
-8555, ACPL ERROR: The 'TX' keyword was expected., 36
-8556, ACPL ERROR: The 'UNTIL' keyword was expected., 36
-8557, ACPL ERROR: The 'USING' keyword was expected., 37
-8558, ACPL ERROR: A user name was expected., 37
-8560, ACPL ERROR: A variable was expected., 37
-8563, ACPL ERROR: The 'ZOOM' keyword was expected., 38
-8564, ACPL ERROR: There is not enough memory., 38
-8565, ACPL ERROR: Cannot open file ., 39
-8566, ACPL ERROR: An illegal character was ignored., 39
-8567, ACPL ERROR: An ACCELL/SQL statement was expected., 39
-8568, ACPL ERROR: An attribute was expected., 40
-8569, ACPL ERROR: A form code section name was expected., 40
-8573, ACPL ERROR: Either the 'KEY' or 'VALUES' keyword was expected., 40
-8575, ACPL ERROR: The 'CASE' or 'DEFAULT' keyword was expected., 41
-8577, ACPL ERROR: The 'CHANGES' keyword was expected., 41
-8578, ACPL ERROR: There was an internal parser error., 41
-8580, ACPL ERROR: There was a bad conversion., 41
-8581, ACPL ERROR: There are too many symbols., 42
-8582, ACPL ERROR: No free registers, the expression is too complex., 42

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

-8584, ACPL ERROR: Too many errors, can't continue., 43
-8585, ACPL ERROR: There is a bad system variable., 43
-8587, ACPL ERROR: Table name not found in data dictionary., 43
-8588, ACPL ERROR: No columns can be found., 44
-8590, ACPL ERROR: An expression was expected., 44
-8591, ACPL ERROR: The 'ACTION' keyword was expected., 44
-8592, ACPL ERROR: The 'RECORD' or 'FORM' keyword was expected., 45
-8593, ACPL ERROR: The 'ADD' or 'FIND' keyword was expected., 45
-8595, ACPL ERROR: The variable list doesn't match # of scalar_db_exp's., 45
-8598, ACPL ERROR: The 'FIRST' keyword was expected., 46
-8599, ACPL ERROR: Language section not valid in a Standard Form., 46
-8600, ACPL ERROR: The CONSTANT expression was expected., 46
-8601, ACPL ERROR: More than one default expression in switch statement., 47
-8602, ACPL ERROR: There is an UNDEFINED function., 47
-8603, ACPL ERROR: The number of parameters do not match., 47
-8604, ACPL ERROR: A result parameter was expected., 48
-8605, ACPL ERROR: A function was redeclared., 48
-8607, ACPL ERROR: 'TO' keyword expected after the keywords 'ON CLEAR'., 48
-8611, ACPL ERROR: There was an error in a control structure break call., 49
-8613, ACPL ERROR: 'SET_CONSISTENCY' or 'RECORD_CONSISTENCY' keyword expected., 49
-8614, ACPL ERROR: A 'FIND', 'NEXT' or 'PREVIOUS' keyword was expected., 49
-8615, ACPL ERROR: A PIPELINE was expected., 50
-8616, ACPL ERROR: Statement can occur only in an ON FIELD code section., 50
-8617, ACPL ERROR: There is a bad function type., 50
-8618, ACPL ERROR: A target attribute is not allowed., 51
-8619, ACPL ERROR: Statement can occur only in an ON FIND code section., 51
-8620, ACPL ERROR: The 'OPERATION' keyword was expected., 51
-8624, ACPL ERROR: Statement may not occur in an ON FIND code section., 52
-8625, ACPL ERROR: Statement may not occur in an INIT FIELD code section., 52
-8626, ACPL ERROR: Statement may not occur in an AFTER APPLICATION code section., 52
-8627, ACPL ERROR: Statement may not occur in a BEFORE APPLICATION code section., 53
-8628, ACPL ERROR: Statement may not occur in a WHEN FIELD CHANGES code section., 53
-8629, ACPL ERROR: Statement may not occur in a BEFORE FORM code section., 53
-8630, ACPL ERROR: There is a bad master application variable., 54
-8631, ACPL ERROR: There are too many program names (pipes) in the program list., 54

261
-8632, ACPL ERROR: The statement may not occur in current code section., 54
-8633, ACPL ERROR: The 'Screen' keyword was expected., 54
-8634, ACPL ERROR: Must use START TX in an application., 55
-8635, ACPL ERROR: There was a duplication of code section., 55
-8637, ACPL ERROR: The 'BY' keyword was expected., 55
-8639, ACPL ERROR: String constants exceeded the maximum number for a form., 56
-8640, ACPL ERROR: Exceeded maximum allowed nesting level., 56
-8641, ACPL ERROR: The 'RETURN' keyword was expected., 56
-8643, ACPL ERROR: The 'FUNCTIONS' keyword was expected., 57
-8644, ACPL ERROR: The 'ON' keyword was expected., 57
-8645, ACPL ERROR: Invalid function key number., 57
-8646, ACPL ERROR: The 'FOR' keyword was expected., 57
-8648, ACPL ERROR: Invalid mode specified., 58
-8649, ACPL ERROR: The 'IS' keyword was expected., 58
-8651, ACPL ERROR: Display variables may not have code sections., 58
-8652, ACPL ERROR: Could not open database., 58
-8657, ACPL ERROR: Could not change to the specified schema or database., 59
-8658, ACPL ERROR: Invalid action specified for NEXT ACTION statement., 60
-8659, ACPL ERROR: The token WORK was expected., 60
-8661, ACPL ERROR: "IS UNDEFINED" was expected., 61
-8662, ACPL ERROR: The keyword NULL is not permitted in this context., 61
-8663, ACPL ERROR: NULL or UNDEFINED expected., 61
-8664, ACPL ERROR: NULLDATE token expected in compatibility mode only., 61
-8665, ACPL ERROR: Error creating 'object_file', error number os_error., 62
-8666, ACPL ERROR: Error reading 'object_file', error number os_error., 62
-8667, ACPL ERROR: Error adding 'object_file', error number os_error., 62
-8668, ACPL ERROR: Error closing 'object_file', error number os_error., 62
-8669, ACPL ERROR: Fatal preprocessor error in 4GL script script_file., 63
-8671, ACPL ERROR: Use of 'FROM' clause is valid only with 'DISPLAY HELP'., 63
-8672, ACPL ERROR: Could not get database information., 63
-8673, ACPL ERROR: Type cannot be specified in a function's local clause., 63
-8674, ACPL ERROR: Type cannot be specified for an attribute., 64
-8675, ACPL ERROR: Type cannot be specified for an external variable., 64
-8676, ACPL ERROR: Type can only be specified for a target variable., 64
-8677, ACPL ERROR: Type specified does not match target column's type., 64
-8678, ACPL ERROR: The 'VALUES' keyword was expected., 64
262
Numeric Index
-8679, ACPL ERROR: Object name is ambiguous - found in more than one schema., 65
-8681, ACPL ERROR: Call of a row-valued stored procedure in an expression., 65
-8682, ACPL ERROR: Programmable function keys are no longer supported., 65
-8683, ACPL ERROR: Duplicate command key(s) attribute clause., 65
-8684, ACPL ERROR: Duplicate ACTION command attribute clause., 66
-8685, ACPL ERROR: Duplicate AUD_ACTION command attribute clause., 66
-8686, ACPL ERROR: Duplicate FIND_ACTION command attribute clause., 66
-8687, ACPL ERROR: Duplicate LABEL command attribute clause., 67
-8688, ACPL ERROR: Duplicate AUD_LABEL command attribute clause., 67
-8689, ACPL ERROR: Duplicate FIND_LABEL command attribute clause., 67
-8692, ACPL ERROR: No command name was specified., 68
-8693, ACPL ERROR: A string constant was expected., 68
-8694, ACPL ERROR: Illegal command action attribute value., 69
-8695, ACPL ERROR: Bad timer function declaration., 69
-8696, ACPL ERROR: Timer functions must be global and declared in EXTERN statements., 69
-8697, ACPL ERROR: Invalid timer function reference., 70
-8698, ACPL ERROR: A TIMER keyword was expected., 70
-8699, ACPL ERROR: An EVENT keyword was expected., 70
-8700, ACPL ERROR: An EVENTS keyword was expected., 71
-8701, ACPL ERROR: Number of seconds for timer event was expected., 71
-8702, ACPL ERROR: The HANDLER keyword was expected., 71
-8703, ACPL ERROR: A COMMAND keyword was expected., 72
-8704, ACPL ERROR: A QUEUE keyword was expected., 72
-8705, ACPL ERROR: A command name was expected., 72
-8706, ACPL ERROR: A timer function name was expected., 73
-8707, ACPL ERROR: A timer function must be an ACCELL/SQL function., 73
-8708, ACPL ERROR: Operation cannot be performed on this command., 73
-8709, ACPL ERROR:

: Command not defined., 74
-8710, ACPL ERROR: Duplicate button attribute clause., 74
-8712, ACPL ERROR: A USERMENU keyword was expected., 74
-8713, ACPL ERROR: A button option was expected., 75
-8714, ACPL ERROR: The '[' token was expected., 75
-8715, ACPL ERROR: The 'TO' keyword was expected., 75
-8716, ACPL ERROR: The ']' token was expected., 75
-8717, ACPL ERROR: The '[' token was unexpected., 76
-8718, ACPL ERROR: Array redefined., 76

263
-8719, ACPL ERROR: Invalid array dimension type., 76

-8720, ACPL ERROR: REF parameters cannot be passed to C-hooks or system functions., 76
-8721, ACPL ERROR: Invalid number of dimensions., 76
-8722, ACPL ERROR: The 'LIST' or 'MATRIX' keyword was expected., 77
-8724, ACPL ERROR: Invalid context for SELF., 77
-8725, ACPL ERROR: A REFERENCE parameter was expected., 77
-8726, ACPL ERROR: A LIST array name was expected., 77
-8727, ACPL ERROR: A MATRIX array name was expected., 78
-8728, ACPL ERROR: Invalid syntax for array attribute., 78
-8729, ACPL ERROR: An array attribute was not expected., 78
-8730, ACPL ERROR: Invalid array dimensions., 78
-8731, ACPL ERROR: Array dimensions were not expected., 79
-8732, ACPL ERROR: Array subscript was out of bounds., 79
-8733, ACPL ERROR: Invalid array reference., 79
-8735, ACPL ERROR: The 'LIST' or 'MATRIX' keyword was expected., 80
-8736, ACPL ERROR: Invalid array subscript., 80
-8737, ACPL ERROR: A form attribute was not expected., 80
-8738, ACPL ERROR: The 'FORMS' or 'FUNCTIONS' keyword was expected., 80
-8739, ACPL ERROR: Database privilege expected., 80
-8740, ACPL ERROR: Database object name expected., 81
-8741, ACPL ERROR: Invalid SQL command., 81
-8742, ACPL ERROR: System Error., 81
-8743, ACPL ERROR: Missing SQL statement terminator., 81
-8744, ACPL ERROR: Statement must be within an executing block., 82
-8745, ACPL ERROR: Illegal command on non-updatable table or view., 82
-8746, ACPL ERROR: The number of set variables and selected columns do not match., 82
-8747, ACPL ERROR: No FROM clause in SELECT statement., 83
-8750, ACPL ERROR: The 'FILE' keyword was expected., 83
-8751, ACPL ERROR: Invalid data type specified for RETRIEVE statement., 83
-8759, ACPL ERROR: Old style database column name, remove '#'., 83
-8760, ACPL ERROR: Clear to Add/Find expressions cannot be set using set/select., 84
-8761, ACPL ERROR: Clear to Add/Find expressions cannot be used in nested set statements., 84
-8762, ACPL ERROR: EXECUTING clause can only be used with a ROW_VALUED stored procedure., 85
-8763, ACPL ERROR: Number of user functions exceeds maximum allowed., 85
-8765, ACPL ERROR: ACCELL/SQL objects may not be used in a DDL command., 85
-8769, ACPL ERROR: Too many characters in a single token., 85

-8772, ACPL ERROR: Type returned does not match function definition return type., 86
-8800, There are no errors to report., 87
-8801, There is not enough memory to activate the form., 87
-8802, The file is not in the proper format., 87
-8803, There has been an internal system error., 88
-8804, There is not enough memory to continue processing., 88
-8805, User has improper permission to access the file., 88
-8806, There has been an I/O error detected by the system., 88
-8807, There are too many active windows., 89
-8808, The form cannot be displayed at the specified location., 89
-8809, The specified form cannot be found in the form archive., 89
-8810, An arithmetic overflow has occurred in a code section of the current form., 90
-8811, An arithmetic underflow has occurred in a code section of the current form., 90
-8812, The specified value is not in the correct DATE format., 90
-8813, The current operation requires more heap memory than available., 91
-8814, The specified file cannot be found., 91
-8815, The data types for this operation do not match., 91
-8816, The value's data type is incorrect for this operation., 92
-8817, A division by zero is not allowed., 92
-8818, The help form archive file cannot be found., 92
-8819, The help form cannot be found in the help archive file., 93
-8826, The form referenced in the code section is not active., 93
-8827, A reference has been made to a non-existent external symbol., 93
-8828, The referenced ACCELL/SQL help file cannot be found or is not readable., 93
-8829, The ACCELL/SQL help sub-system file cannot be found or is not readable., 94
-8830, The referenced help form has too many 'next forms' associated with it., 94
-8831, The referenced help form cannot be found in the help description file., 94
-8832, A command sequence is linked to more than one command in the unicap file., 94
-8834, There are no records in the selected set., 95
-8835, This is the last record., 95
-8836, This is the first record., 95
-8837, This is the last set., 95
-8838, This is the first set., 95
-8839, The specified search criteria is invalid., 96
-8840, The justification specifier is invalid., 96
-8841, The current record cannot be deleted., 96

265
-8842, Cannot open the application '.al' map file., 96

-8843, Cannot read the application '.al' map file., 97
-8844, The unicap file could not be opened., 97
-8845, There is no 'next form' for this form., 97
-8847, The referenced C-hook function cannot be found., 98
-8848, Bad heap size parameter: size., 98
-8849, Bad number of windows parameter: size., 98
-8850, Bad stack block size parameter: size., 98
-8852, ACCELL/SQL is unable to open the error file 'file_name'., 99
-8853, A reference has been made to an invalid screen field name., 99
-8854, The referenced form is unknown to the Manager., 99
-8855, The database design is different from when the application was created., 100
-8857, Some command definitions are missing from the unicap file., 100
-8858, The main help form is not in the help sub-system description file., 101
-8859, The current record could not be locked. Try again later., 101
-8860, The referenced variable does not refer to a screen field., 101
-8861, The referenced variable is not a target variable., 101
-8862, A subtraction operation was attempted on a string value., 102
-8864, All records in the selected set are locked by another user., 102
-8865, The form name specified in an ERASE TRIM statement has not been displayed., 102
-8866, Trim does not exist., 102
-8874, A CREATE PIPELINE 4GL statement has failed., 103
-8875, A CLOSE PIPELINE 4GL statement has failed., 103
-8876, The pipeline variable for a pipe must be of type NUMERIC., 103
-8877, Can't create a CREATE PIPELINE output file., 104
-8878, A CREATE PIPELINE statement program could not be created., 104
-8879, There has been an abnormal pipeline program termination., 104
-8880, Too many or no pipeline tasks have been started., 105
-8881, An invalid display justification type was encountered., 105
-8883, Bad arguments to 4GL system function., 105
-8884, A master application form's NEXT FORM cannot continue a transaction., 105
-8886, Value is undefined., 106
-8887, An invalid variable or database type was detected., 106
-8894, Invalid default justification., 106
-8895, The screen field is not wide enough for the formatted value., 107
-8897, Attempted an arithmetic operation with an old-style NULLDATE value., 107
266
Numeric Index
-8898, The command entered is invalid in the current mode., 108

-8899, The current field is required., 108
-8901, A referenced form is not active. The transaction cannot be restarted., 108
-8902, There is an undefined boolean variable in a statement., 109
-8903, The CLEAR TO FIND command requires at least one searchable field., 109
-8905, Error in WRITE PIPELINE statement. Check operation of pipe programs., 109
-8906, Wrong number of arguments in an ACCELL/SQL function call., 110
-8907, There was a bad type involved in conversion., 110
-8908, The specified value is not in correct TIME format., 110
-8909, The specified value is not in correct BOOLEAN format., 110
-8910, The specified value is not in correct FLOAT format., 111
-8911, The specified value is not in correct NUMERIC format., 111
-8912, The specified value is not in correct AMOUNT format., 111
-8913, Could not open database., 112
-8914, Could not close database., 112
-8916, Could not commit a transaction., 113
-8920, Date initialization failed., 113
-8921, Operating system interrupt handler problem., 113
-8922, The function key specified is not known to this form., 113
-8930, Internal problem with null values., 113
-8931, The keyword NULL appears in an invalid ACCELL/4GL context., 114
-8932, Cannot switch to or obtain information on a schema., 114
-8933, Cannot obtain information on a user., 115
-8936, Cannot open application database map file., 115
-8937, The resultant string has overflowed the display format., 115
-8938, The input string is invalid for the given data type., 115
-8939, Not all required fields have been entered - ADD REJECTED., 116
-8940, Mapping of C-hook functions failed when opening the database., 116
-8941, A commit or abort of a transaction has failed., 117
-8942, An invalid regular expression was passed to reg_exp_str_compare$()., 117
-8943, Null values are not supported in the underlying database., 117
-8944, ACCELL/SQL cannot run on this size of terminal., 117
-8945, Error initializing ACCELL/SQL environment: os_error., 118
-8946, Illegal initial memory size: size., 118
-8947, Illegal maximum sort memory size: size., 118
-8948, Illegal selected set directory name: directory_name., 118
Numeric Index
267
-8950, Can't initialize mode messages, see error file., 119

-8951, Could not read the error message archive (SERRORS)., 119
-8952, Illegal number of open archives ., 119
-8953, Command line access level must be between and ., 119
-8954, CLEAR_FIND_EXP attribute's type does not match target field's type., 120
-8955, The specified help form could not be found in the specified help archive., 120
-8956, Record number is outside of the current selected set., 120
-8957, Invalid value for this statement., 121
-8958, Could not get database information., 121
-8959, Invalid Username/Password., 121
-8960, Invalid number of zoom values returned., 121
-8961, The record has changed since the last read., 122
-8962, The record you are attempting to update or delete has been deleted., 122
-8963, The record you are attempting to position on has been deleted., 123
-8965, Unable to validate licensing information., 123
-8966, The data type in the C-hook return value is invalid., 123
-8967, An X Window toolkit error occurred., 124
-8970, Invalid setting of ACLPRESMODE configuration variable., 124
-8971, Illegal command action specifier string., 124
-8972, Illegal label action specifier string., 124
-8973, An illegal key string was assigned to a command's key attribute., 125
-8974, An illegal function key number was encountered., 125
-8975, Busymouse file read error., 126
-8976, Bad form location coordinates., 126
-8977, A bad timer id(s) was encountered in the delete timer statement., 126
-8979, Illegal timer function argument., 126
-8980, Timer event creation failed., 127
-8981, Queued command execution failed., 127
-8982, Queued command not enabled in current mode., 128
-8983, An invalid button location has been given., 128
-8984, Invalid line number was specified., 129
-8985, Invalid field name was specified., 129
-8986, Invalid arguments specified with this command., 129
-8987, 'TO' keyword missing on the command line., 129
-8988, Invalid value was specified., 130
-8989, There is no active form., 130

-8990, Invalid form attribute or field name was specified., 130

-8991, Invalid field attribute was specified., 130
-8992, Invalid form name was specified., 130
-8993, Invalid break point was specified., 131
-8994, Invalid debugger license., 131
-8995, Invalid current line no., 131
-8996, Invalid command from a file., 131
-8997, Invalid Presentation Mode specified for the ACCELL/SQL Debugger., 131
-8998, Invalid file name was specified., 132
-8999, Invalid debugger command was specified., 132
-9000, Array subscript out of bounds., 133
-9001, Invalid type for array subscript., 133
-9002, Cannot reference an undefined array., 133
-9003, Subscript is missing from array reference, value is undefined., 134
-9004, Invalid array dimensions., 134
-9005, There is not enough memory to grow an unbounded array., 134
-9006, Clear to add expressions are not supported for unbounded arrays., 134
-9007, The parameter types for an ACCELL/SQL function call do not match., 135
-9008, Invalid attribute, a scalar cannot reference an array attribute., 135
-9009, Invalid attribute, a list array cannot reference a matrix attribute., 135
-9010, Invalid attribute, a matrix array cannot reference a list attribute., 135
-9011, Invalid array subscript., 136
-9012, Invalid array subscript, missing right bracket., 136
-9013, Illegal form cache size: size., 136
-9014, Illegal global function cache size: size., 136
-9015, An invalid stack address was encountered., 136
-9016, The referenced identifier does not refer to a form., 137
-9017, The current form is read only, insert/update/delete not allowed., 137
-9018, Operation not allowed., 137
-9019, Illegal variable length data in-memory limit: length., 138
-9020, Illegal variable length data file directory name: directory_search_path., 138
-9021, Illegal maximum number of open variable length data files: number., 138
-9024, There was an error while reading/accessing a variable length data file., 139
-9025, There was an error while writing to a variable length data file., 139
-9026, A file that was to be created already exists., 140
-9027, An expression or variable must be of type TEXT or BINARY., 140
Numeric Index
269
-9028, Invalid value was specified for WINDOW_HEIGHT field attribute., 140
-9033, Insufficient heap memory to display text in field., 141
-9034, Insufficient heap memory to edit text in field. Use system editor., 141
-9035, Last operation required more heap than available. Last edit lost., 141
-9036, Insufficient heap size to edit the current text line. Adjust heap size., 142
-9037, The record you are attempting to position on has an undefined row id., 142
-9038, The record you are attempting to read has an undefined row id., 143
-9039, A record you are attempting to read has been deleted., 143
-9040, Invalid value for $info_level. Setting $info_level to 1 (intermediate)., 143
-9041, Invalid value specified for a screen field's COL attribute., 143
-9042, Invalid value specified for a screen field's ROW attribute., 144
-9046, The data type being returned does not match the function definition., 144
-9047, A variable's CLEAR_ADD_EXP was set on an invalid form., 144
-9048, A Row ID is required for the current operation., 144
-9100, The input value is not within the valid field range., 145
-9101, There is no trim to delete., 145
-9103, There isn't enough room on the form to insert a new line., 145
-9104, No more characters can be inserted. The current line is full., 146
-9105, Cursor is at left edge of form. You cannot move any farther left., 146
-9106, Cursor is at right edge of form. You cannot move any farther right., 146
-9109, Form is at left edge of window. It cannot be moved left any more., 146
-9110, Form is at right edge of window. It cannot be moved right any more., 147
-9111, Form is at top edge of window. It cannot be moved up any more., 147
-9112, Form is at bottom edge of window. It cannot be moved down any more., 147
-9113, Unreplace commands can only be used while in replace mode., 147
-9114, The cursor cannot move left any more., 148
-9115, The cursor cannot move right any more., 148
-9116, The cursor cannot move up any more., 148
-9117, The cursor cannot move down any more., 148
-9118, A field does not exist at the current position., 149
-9119, An invalid character has been entered., 149
-9120, An invalid character has been entered as a graphics character., 149
-9121, Unreplace cannot be used while the cursor is on a screen field., 149
-9122, A field cannot be created on top of existing trim., 150
-9123, Trim cannot be placed on top of an existing field., 150
-9125, Cannot move farther left. The form is at the leftmost window edge., 150

-9126, Cannot move farther right. The form is at the rightmost window edge., 150
-9127, Cannot move farther up. The form is at the topmost window edge., 151
-9128, Cannot move farther down. The form is at the bottommost window edge., 151
-9129, Form's left border cannot be moved left any more due to existing trim., 151
-9130, Form's bottom border cannot be moved up any more due to existing trim., 152
-9132, Trim cannot be inserted while on a screen field., 152
-9133, Use the DELETE FIELD command to remove a screen field., 152
-9134, DELETE cannot be used in the middle of a field., 152
-9135, Field cannot be moved here because it will overlap an existing field., 153
-9136, The field cannot be moved here because it will overlap existing trim., 153
-9137, The command just entered is not recognized., 153
-9138, An error occurred while trying to delete the form file., 153
-9139, An error occurred while trying to write the backup form file., 154
-9140, An error occurred while trying to write the temporary form file., 154
-9141, An error occurred while trying to write a help file., 154
-9143, An error occurred while linking a temporary file to the current file., 154
-9145, An invalid value has been entered., 155
-9146, A field on this form requires input before the form can be updated., 155
-9147, The only valid entries for this field are - Yes or No., 155
-9148, This isn't a valid field data type. Please reenter the data type., 155
-9149, Invalid justification type. Please reenter the justify type., 156
-9150, A field's input length must be greater than zero. Please reenter a value., 156
-9151, The specified input length is too long. Please reenter a new value., 157
-9153, This field name is already used for another field on this form., 157
-9154, This isn't a valid edit mode. Edit modes are Replace or Insert., 157
-9155, The form must be made larger before additional trim can be added., 157
-9156, Only the characters 'T' or ' ' (space) can be used on this form., 158
-9157, The requested command is inactive in current mode., 158
-9158, Fixed trim cannot be marked within non-repeating trim., 158
-9160, The specified database table name cannot be found in the database., 158
-9161, An error has been generated from an RDBMS function., 159
-9162, This isn't a valid order entry. Ordering can be by Row or Column only., 159
-9163, An invalid scroll bar position has been entered., 159
-9166, The specified field name cannot be found in the target table., 160
-9167, No target table has been specified for this form., 160
-9169, Transaction levels can only be within the range of 1-5., 160

271
-9170, Blanks cannot be used in field names. Please reenter a field name., 161
-9171, Blanks cannot be used in file names. Please reenter the file name., 161
-9172, The database has been changed. Use EXPLAIN ERROR for more information., 161
-9173, The file name is too long. File names are limited to 14 characters., 161
-9174, Invalid case conversion type has been entered., 162
-9175, An error occurred while trying to open a window., 162
-9176, The screen field length is longer than the target field length., 162
-9177, Only a start transaction is allowed from an application form., 163
-9200, An error occurred while opening the form., 163
-9201, An error occurred while reading the form., 163
-9202, An error occurred while closing the form., 163
-9206, An error occurred while trying to open a screen field help file., 164
-9207, An error occurred while closing a screen field help file., 164
-9208, An error occurred while reading an existing screen field help file., 164
-9209, An error occurred while writing a screen field help file., 164
-9213, Not enough memory on the heap to write the form., 165
-9216, An error occurred while trying to unlink a screen field help file., 165
-9217, An error occurred while trying to link a screen field help file., 165
-9218, An error occurred while activating the form., 165
-9219, There was an error initializing the keyboard information., 166
-9220, There was an error initializing the window manager., 166
-9221, An error occurred while opening internal form file: Field.frm, 166
-9222, An error occurred while reading internal form file: Field.frm, 166
-9223, An error occurred while closing internal form file: Field.frm, 167
-9225, An error occurred while trying to open window: window_id., 167
-9231, frminit: Error from wnopen., 167
-9235, ASCEND or DESCEND are the only valid entries for this field., 168
-9237, An error occurred while opening a SGLPNT temporary help file., 168
-9238, An error occurred while reading a SGLPNT temporary help file., 168
-9239, An error occurred while writing a SGLPNT temporary help file., 169
-9241, A Generator temporary help file could not be opened., 169
-9242, Unable to open the Generator's temporary file., 169
-9243, The Generator has run out of memory., 169
-9244, Internal error while sizing form., 169
-9245, Internal error while opening a window., 170
-9247, Unable to execute the system editor., 170
272
Numeric Index
-9248, Could not close the database., 170

-9252, Could not open the database., 171
-9253, Could not change to the specified schema or database., 171
-9254, The UNIFY configuration variable is not set., 172
-9255, Could not create a master application form., 172
-9256, Could not remove a file., 172
-9260, WARNING! Target table and field information has been cleared., 172
-9263, Not all fields can be accommodated in the default form., 173
-9265, This array name is already used for another array on this form., 173
-9266, Unable to change array class from Matrix to List., 173
-9267, Invalid array class. Array classes are Matrix and List., 174
-9268, This array cell is already referenced by another field on this form., 174
-9269, Cannot delete array with existing screen field references., 174
-9270, Blanks cannot be used in array names. Please reenter an array name., 174
-9271, This array name is already used for a field on this form., 174
-9272, Target field names cannot be used for array names., 175
-9273, Operation is invalid in middle of a multi-line text field., 175
-9274, Invalid screen field name., 175
-9275, The binary data type cannot be used for form screen fields., 176
-9276, Blanks cannot be used in form names. Please reenter a form name., 176
-9277, Field name from this table already used as a screen field or array., 176
-9278, Entire text field must be within, or outside of the repeating area., 176
-9279, This field name is already used as a sort field., 176
-9280, The form is too large for the terminal screen., 177
-9281, Find count must be greater than or equal to 0., 177
-9300, Out of memory., 178
-9301, Error opening file:
., 178
-9302, Error reading file:
., 178
-9303, Error writing file:
., 178
-9304, Error closing file:
., 179
-9305, Error creating file:
., 179
-9307, Warning - No target table name given., 179
-9308, Warning - Invalid target table name given., 179
-9309, Warning,
was a column in the target table, but is not now., 180
-9310, Invalid transaction token., 180

273
-9311, Warning - Invalid ACCELL/SQL TYPE specified: data_type., 180

-9312, Unexpected End-Of-File encountered., 180
-9313, Unexpected token encountered: token_string., 181
-9314, Indeterminate window manager error., 181
-9315, Indeterminate error while reading target table information., 181
-9317, Could not open database - continuing without database information., 182
-9318, Warning, type for column 'column_name' changed in database, type being changed for target variable.,
182
-9319, Warning, length for column 'column_name' changed in database, length being changed for target
variable., 182
-9320, Warning, 'column_name' was not a target column in the target table, but is now., 183
-9321, Warning, old rhli type encountered for 'column_name', ascii file needs to be upgraded., 183
-9322, Field array cell subscript out of bounds: array_name., 183
-9323, FIELD_CLASS statement for an undefined array: array_name., 183
-9324, Unexpected field input length specification encountered., 183
-9325, Unexpected field window height specification encountered., 184
-9701, Invalid error number., 184
-9709, Insufficient memory available., 184
-9710, Unknown or invalid value in switch., 184
-9726, file open error:, 184
274
Numeric Index

Unify Error Messages

Caricato da

Informazioni sul documento

Descrizione:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Descrizione:

Copyright:

Formati disponibili

Unify Error Messages

Caricato da

Descrizione:

Copyright:

Formati disponibili

R

E   

(79 :3),7  

Error Message Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ACCELL/SQL Combiner (ACMB) Error Messages . . . . . . . . . . . . . . . .

ACCELL/SQL Linker (ALNK) Error Messages . . . . . . . . . . . . . . . . . . .

ACCELL/SQL Compiler (ACPL) Error Messages . . . . . . . . . . . . . . . . .

ACCELL/Manager (AMGR) Error Messages . . . . . . . . . . . . . . . . . . . . .

ACCELL/SQL Interactive Debugger Error Messages . . . . . . . . . . . . . .

ACCELL/Manager Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ACCELL/Generator (AGEN) Error Messages . . . . . . . . . . . . . . . . . . . .

ACCELL/SQL Utilities Error Messages . . . . . . . . . . . . . . . . . . . . . . . . .

ACCELL/SQL Report Writer (RPT) Error Messages . . . . . . . . . . . . . . .

ACCELL/SQL Menu Handler Error Messages . . . . . . . . . . . . . . . . . . . .

ACCELL/SQL RDBMS Interface Error Messages . . . . . . . . . . . . . . . . .

This manual uses various graphic conventions to help you easily

Represents the return key. This key could be labeled as

This manual uses the following syntax conventions to describe the

Boldface words are command keywords or literal strings

Italic words indicate words, variables, numbers, or

UPPERCASE words are ACCELL/SQL keywords.

type either uppercase or lowercase letters.

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

Non-bold square brackets indicate that the enclosed word

Vertical bars that enclose a stacked list of options mean

Ellipsis points indicate that you may repeat the

Error Message Descriptions

   

    

The error message number corresponds to the number of the error

Error Message Descriptions

ACCELL/SQL Combiner (ACMB) Error

SAR ERROR: There is a corrupt archive file archive_name.

SAR ERROR: Cannot open archive_name, error number os_error.

SAR ERROR: Cannot create archive_name, error number os_error.

ACCELL/SQL Combiner (ACMB) Error Messages

The ACCELL/SQL combiner (ACMB) failed to close the temporary

If this error persists, contact Unify Customer Support.

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

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

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

The ACCELL/SQL combiner (ACMB) cannot read an ACCELL/SQL form

ACMB ERROR: There was a bad magic number.

The ACCELL/SQL combiner (ACMB) has encountered an unknown

ACCELL/SQL Combiner (ACMB) Error Messages

This error can occur in these cases:

ACMB ERROR: The Combine failed in malloc memory.

The ACCELL/SQL combiner (ACMB) has run out of memory while

ACMB ERROR: Couldnt find a next field.

When the ACCELL/SQL generator creates an ACCELL/SQL form file (a

When the ACCELL/SQL combiner (ACMB) is processing a form that has

ACCELL/SQL Combiner (ACMB) Error Messages

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, it

ACMB ERROR: There was a form name mismatch.

When the ACCELL/SQL combiner (ACMB) is processing a form that has

ACCELL/SQL Combiner (ACMB) Error Messages

ACMB ERROR: There was a form/application mismatch.

When the ACCELL/SQL combiner (ACMB) is processing a form that has

ACMB ERROR: There is a corrupt file.

The ACCELL/SQL combiner (ACMB) cannot read all or part of the

E

(79 :3),7