Client Messages
All messages documented in this section will be displayed only if you switch on error logging and command prompting by issuing these commands:
$OPTION LOCKERR OFF
$OPTION LOCKPROMPT OFF
If the message you are looking for does not appear in this section, look for it elsewhere in this topic, particularly in Messages from Client and Server, which also includes messages from the communication layer (RCI).
E004 <command> is an invalid command
|
Explanation:
|
You have called a procedure that Rochade could not find in the procedure database, or you have called an invalid RPL command. |
|
Action:
|
Check the call. If you are calling a procedure, it must exist within one of the databases that you declared as procedure databases when you started the client. |
E006 Error in writing item
|
Explanation:
|
The reason can be memory shortage, a disk error, or an inconsistent database. This error can also occur in connection with the $WSAM command. In that case, either the file name is invalid or the file is write-protected. |
E007 Error in writing file <file>
|
Explanation:
|
This message appears when an error occurs while a sequential file is being written. The cause could be lacking access rights, or some disk error, etc. |
|
Action:
|
Check the access rights and disk. |
E008 Command number <no> is out of range
|
Explanation:
|
You have made changes in the COMMANDS system table. |
|
Action:
|
Recall the value range for RPL commands, ranging from 0001 to 0174. |
E011 No current work area exists
|
Explanation:
|
Because of memory shortage or disk errors on your system, no work area could be opened. |
|
Action:
|
Check your system resources. |
E012 The attribute <i_tp> <i_nm> <attr> cannot be read completely
|
Explanation:
|
Because of memory shortage or disk errors on your system, the specified attribute could not be read completely. |
|
Action:
|
Check your system resources. |
E016 Attribute <i_tp> <i_nm> <attr> cannot be deleted
|
Explanation:
|
You have tried to delete the DOCIDENT or DEFINITION attribute of an item. |
|
Action:
|
These two attributes of an item must not be deleted. |
E017 Item <i_tp> <i_nm> does not exist
|
Explanation:
|
You attempted to read an item that does not exist in the current database. This message can occur when you read value attributes or when, within report commands, you access an item type that is not visible on the basis of the currently loaded system tables or does not exist in the current database. |
|
Action:
|
Check the item name. Check whether the database selected via $SELDB is in fact the database you want to work with and if the item exists in this database ($SDC command). Check whether the item type exists in your system tables. |
E018 Attribute type <attr> is not known
|
Explanation:
|
You attempted to read an item that is not contained in the CHAPTYPS system table assigned to you. |
|
Action:
|
Check the system tables with which you are working. |
E019 Attribute <i_tp> <i_nm> <attr> does not exist
|
Explanation:
|
You attempted to read an attribute that does not exist in the specified item. |
E020 Item type <i_tp> is not known
|
Explanation:
|
The specified item type is not contained in the DOCTYPS system table assigned to you. |
|
Action:
|
Check the system tables with which you are working. |
E022 Item <i_tp> <i_nm> has been deleted
|
Explanation:
|
You have attempted to read an item that was deleted using the $ER command, or you have attempted to delete it again using $ER. |
E023 <str>: Invalid input - please retry
|
Explanation:
|
You have not selected one of the input values specified by Rochade. |
|
Action:
|
Reread the input prompt and enter one of the specified values. |
E024 <command>: Work area not defined
|
Explanation:
|
The $REDLN and $FREELN commands require specification of a work area. |
|
Action:
|
Check the command call and specify the work area as required. |
E025 Item <i_tp> <i_nm> is active or an alias name exists
|
Explanation:
|
You attempted to rename an item, but the new name already belongs to an active item or exists as an alias name. |
|
Action:
|
Check your command call. Choose a new item name. |
E029 <cmd>: Too few parameters specified
|
Explanation:
|
You have not specified enough parameters in a command call. |
|
Action:
|
Check your command call. See the ASG-Rochade Programmer’s Guide Volume 1 for the correct command format. |
E030 Item type <i_tp> is not in the search path
|
Explanation:
|
In your $CDOC command, you specified an item type that has not been defined in the query path. |
|
Action:
|
Check your command call, and check whether the specified item type has been entered into the query path table using $INDOC or $DQCMD. |
E031 Warning: Attribute selection table overflow
|
Explanation:
|
You have specified more than 20 different attributes using $INCHAP and/or $EXCHAP commands. |
|
Action:
|
Check the $INCHAP and $EXCHAP commands in your procedure. You must not exceed the maximum number of 20 different attributes. |
E032 <cmd>: Warning: String selection table overflow
|
Explanation:
|
You have specified more than 20 different item types using $INLINK, $EXLINK, $INPROP and/or $EXPROP commands. |
|
Action:
|
Check the $INLINK, $EXLINK, $INPROP, and $EXPROP commands in your procedure. The maximum number of 20 different attributes must not be exceeded. |
E034 $LIST: No temporary sort work area available
|
Explanation:
|
There is not enough memory available on your client PC to execute the $LIST command. |
|
Action:
|
Check the system resources on your client PC. |
E037 <user> is not a valid user
|
Explanation:
|
This message appears only in batch mode; it appears if the USER item specified in $MOVELOG does not exist in the selected database. |
|
Action:
|
Make sure the user name is entered correctly. If the problem persists, contact your database administrator. He can check if a USER item for the user in question exists in the specified database. |
E038 Error in loading system tables of user <user>
|
Explanation:
|
Your system tables are either corrupted or you have made changes in them without following the correct syntax. |
E039 Overflow in system table: <sys_tab>
|
Explanation:
|
There is not enough memory available on your client PC to load the system tables. |
|
Action:
|
Check the system resources on your client PC. |
E041 <command>: Current work area is empty
|
Explanation:
|
The command specified in <command> requires that the current work area has some content. For instance, if you want to write a text attribute for an item, the work area must contain the attribute content. |
|
Action:
|
Provide a work area with appropriate content for the command. |
E044 Error in calling editor: <editor>
|
Explanation:
|
The specified external editor either does not exist on your PC or is not in the system path of your operating system. |
|
Action:
|
Check the value of the global Rochade variable $EDIT; check whether your editor is in the system path. |
E047 $FORM: Error in opening temporary work area
|
Explanation:
|
The $FORM command requires internal processing memory. There is not enough memory available on your client PC. |
|
Action:
|
Check the system resources on your client PC. |
E048 Not allowed to write to DOCIDENT attribute
|
Explanation:
|
Users are not allowed to write to the DOCIDENT text attribute. |
E049 <command>: Item name NIL is not permitted
|
Explanation:
|
You attempted to write an item with the name NIL. NIL is not permitted as an item name in Rochade. |
E051 $CDOC: Overflow <str>
|
Explanation:
|
The $CDOC command requires internal processing memory. There is not enough memory available on your client PC. |
|
Action:
|
Check the system resources on your client PC. |
E059 Alias item <i_tp> <i_nm> does not exist
|
Explanation:
|
The specified item name is not an alias name for an item. |
|
Action:
|
Check the command call. |
E060 Invalid line number
|
Explanation:
|
This error occurs if an invalid line number is used in a $CHANGE command. The $CHANGE command is described in the ASG-Rochade Programmer’s Guide Volume 1. |
|
Action:
|
Check what you specified in the $CHANGE command, and check if the work area contains the specified line or character string. |
E061 Inhibit flag is not permitted
|
Explanation:
|
This error can occur when working under BS2000 and using the $EDIT command with the inhibit flag. |
|
Action:
|
Check if you have taken into account all operating system specific details in your editor call. For information, see the system literature of BS2000. |
E101 ROCHADE command not permitted: $GO in line: <ln> column: <col>
|
Explanation:
|
This message appears if you specified a $GO command in a procedure source code and submit this to the preprocessor. |
|
Action:
|
Avoid the use of $GO constructs and use Rochade's flow control instructions (IF ... THEN, WHILE, FOR, SWITCH, and REPEAT). |
E102 Constant value not permitted
|
Explanation:
|
The SWITCH keyword is followed by a constant value. |
|
Action:
|
Check whether you forgot to prefix the name of the variable with a colon. |
E103 FOR statement: Argument is not numeric
|
Explanation:
|
The variable for counting in a FOR loop contains a non-numerical value. |
|
Action:
|
Check the value assignment for the variable. |
E105 Syntax error in line: <ln> column:<col> > <col> <
|
Explanation:
|
A syntax error occurred during preprocessing of your procedure. Using the line and column numbers, you can find the exact location. |
|
Action:
|
Check the command syntax in the line and column specified in the message. Errors often occur because of missing or unbalanced parentheses. |
E107 Nesting depth in control structure too large
|
Explanation:
|
This message occurs if the preprocessor ($PRE) runs into problems with flow control structures possessing excessive nesting depth or containing syntax errors (for example, if the procedure source code exceeds the maximum nesting depth 64). |
|
Action:
|
Check syntax and flow control in your procedure. You may need to break procedures into less deeply nested procedures. Also check if all opening and closing parentheses are set correctly. |
E110 System error: Code = <code>
|
Explanation:
|
An internal error occurred in the $PRE command. |
|
Action:
|
Contact ASG Customer Support. |
E111 Invalid BREAK/NEXT statement in line: <ln> column: <col> > <col> <"
|
Explanation:
|
Your procedure contains a A BREAK or NEXT statement that does not belong to a loop or SWITCH...CASE statement. |
|
Action:
|
Check the syntax and positioning of parentheses in your procedure. |
E112 Argument is not numeric in line: <ln> column: <col> > %s
|
Explanation:
|
A syntax error has been found while preprocessing your procedure. The preprocessor expects a numeric value at this point. |
|
Action:
|
Check the command syntax in the line and column specified in the message. |
E119 $SEND: Missing PLUGINS setting in start section <client_start>
|
Explanation:
|
The setting PLUGINS is missing from the section <client_start> of the client initialization file. |
|
Action:
|
Add the setting to the initialization file. For more information, see Configuring Rochade . |
E120 $SEND: Insufficient memory to load external library <library> (<extlib>)
|
Explanation:
|
Insufficient memory is available for dynamically loading the module from the external library specified with <library>=<extlib>. |
|
Action:
|
Check the system resources and make sure that sufficient memory is available at load time. |
E121 $SEND: No appropriate entry point found in external library <library> (<extlib>)
|
Explanation:
|
The entry point RoCreate or a corresponding entry point satisfying the conventions of the operating system that is in use is missing from the library specified in the setting <library>=<extlib>. |
|
Action:
|
Make sure that the specified library contains an appropriate entry point. For more information, see the topic about dynamically loadable libraries in the ASG-Rochade Programmer’s GuideVolume 3. |
E122 System error: Insufficient memory
|
Explanation:
|
There is not enough memory available on your client PC. |
|
Action:
|
Check the system resources on your client PC. |
E123 <proc> cannot be loaded
|
Explanation:
|
An internal error occurred while a procedure was loaded. Possible causes could be insufficient hard disk space or excessive nesting of procedures. |
|
Action:
|
Check the system resources and the nesting depth of your procedures. |
E124 <type> stack overflow
|
Explanation:
|
An overflow of the global, local, or private variable stack occurred. Insufficient system resources could be a possible cause, or you may have exceeded the allowed maximum number of variables. For details on maximum values, see Rochade Update Index. |
|
Action:
|
Check the system resources. Also check whether you have exceeded the maximum number of variables through cyclical procedure calls. |
E125 Procedure stack overflow
|
Explanation:
|
The nesting level of your procedures and actions is to deep. The maximum nesting depth for procedures and actions is 64. |
|
Action:
|
Check the nesting depth for your procedure or class. |
E126 $SEND: No external library assigned to <library> in section <plugins_section>
|
Explanation:
|
For the external library specified in the command $SEND, there is no corresponding library assignment <library>=<extlib> in the section <plugins_section> of the client initialization file. |
|
Action:
|
Make sure that the settings in the section <plugins_section> in the client initialization file correspond to the respective specifications in the $SEND command. |
E127 $SEND: Could not load external library <library> (<extlib>)
|
Explanation:
|
Insufficient memory is available for dynamically loading the module from the external library specified with <library>=<extlib>. The module referenced in the $SEND command via <library> could not be loaded from the external library <extlib>. A possible reason could be that insufficient system resources are available. |
|
Action:
|
Check the system resources and make sure that sufficient memory is available at load time. |
E128 $SEND: Class description <class> not found
|
Explanation:
|
The specified class description does not exist in any of the databases that were declared as procedure databases. |
|
Action:
|
Check whether the database containing the class description has been declared as a procedure database when the client was started. |
E129 $SEND: Cycle in class <class>
|
Explanation:
|
For the class specified in the message, the inheritance hierarchy is incorrect, causing cyclical overloading of the actions. |
|
Action:
|
Check the inheritance hierarchy of your class. This error cannot occur if you use Class Builder as the development tool for classes. |
E130 $SEND: Syntax error in class <class>
|
Explanation:
|
The specified class contains an action that has no name. |
|
Action:
|
Check the actions of the class. Each action must have a name. This error cannot occur if you use Class Builder as the development tool for classes. |
E131 $GRAPHIC: Erroneous parameter <par> in subcommand <command>
|
Explanation:
|
The $GRAPHIC command was not called with all the required parameters. |
|
Action:
|
Check the call syntax of the command for the function specified in <command>. |
E132 $GRAPHIC: Subcommand <command> is not implemented
|
Explanation:
|
The specified subcommand of $GRAPHIC does not exist (maybe a mistake was made when entering the name of a $GRAPHIC subcommand). Therefore it is interpreted as not implemented. $GRAPHIC and its subcommands are described in the ASG-Rochade Programmer’s Guide Volume 2. |
|
Action:
|
Check your entries in the $GRAPHIC command; in particular, check the name of the subcommand in question. |
E133 $GRAPHIC: Parameter for <par> is missing
|
Explanation:
|
The $GRAPHIC command was called with incorrect parameters. |
|
Action:
|
Check the command’s call syntax for the function specified in <command>. |
E134 $GRAPHIC: Invalid keyword <keyword>
|
Explanation:
|
The description work area for the $GRAPHIC command contains an incorrect keyword. |
|
Action:
|
Check the syntax of the work area that you submit as a parameter when calling the $GRAPHIC command. |
E135 $GRAPHIC: Keyword <keyword> in parameter <par> is invalid
|
Explanation:
|
The description work area for the $GRAPHIC command contains a keyword that is incorrect for the specified $GRAPHIC function. |
|
Action:
|
Check the keywords in the work area with regard to the specified function. |
E136 $GRAPHIC: Identifier <id> = <id> already used
|
Explanation:
|
You attempted to create a new graphic object, but its object ID already exists. |
|
Action:
|
Check whether the variable for the object ID of the graphic object is already in use in your application. |
E137 $GRAPHIC: Identifier <id> = <id> does not exist
|
Explanation:
|
You are attempting to access a graphic object that has not been created yet. |
|
Action:
|
Check whether the variable for the object ID of the graphic object contains a valid object ID. |
E138 $GRAPHIC: Keyword <keyword> is invalid
|
Explanation:
|
The description work area for the $GRAPHIC command contains an incorrect keyword. |
|
Action:
|
Check the syntax of the work area that you submitted as a parameter when calling the $GRAPHIC command. |
E139 $GRAPHIC: Resource overflow at keyword <keyword>
|
Explanation:
|
There is not enough memory for the large amount of resources that you use in your application. |
|
Action:
|
Check your system resources and limit the number of resources for $GRAPHIC if necessary. |
E140 $GRAPHIC: Subcommand <command>: Invalid parentheses
|
Explanation:
|
In the description work area for the $GRAPHIC command, parentheses have been positioned incorrectly. |
|
Action:
|
Check the syntax of the work area that you submitted as a parameter when calling the $GRAPHIC command. |
E141 $GRAPHIC: Subcommand <command>: Invalid work area
|
Explanation:
|
The structure of the description work area for the $GRAPHIC command does not conform to the required syntax. |
|
Action:
|
Check the syntax of the work area that you submitted as a parameter when calling the $GRAPHIC command. |
E142 $GRAPHIC: Error in object identifier <objid>
|
Explanation:
|
You specified an incorrect object ID for the graphic object. |
|
Action:
|
Check whether the variable for the object ID of the graphic object contains the correct value. |
E201 $GENC/$GENP: Invalid work area: <wa>
|
Explanation:
|
The $GENP and $GENC commands require a work area with a particular syntax. For detailed information, see the ASG-Rochade Programmer’s Guide Volume 1. |
|
Action:
|
Check the syntax of the work area. |
E202 $GENC/$GENP: Too few parameters specified
|
Explanation:
|
When calling the $GENP and $GENC commands, a work area must be specified. |
|
Action:
|
When calling the command, specify a work area from which to generate the PL/1 or COBOL data structure. |
E203 $MOVELOG: Error in loading USER-EXEC attribute
|
Explanation:
|
There is not enough memory for loading or executing the EXEC attribute of the USER item. |
|
Action:
|
Check your system resources. |
E204 $MOVELOG: Login incorrect, command aborted
|
Explanation:
|
The first $MOVELOG command is incorrect, or you entered the user ID incorrectly three times, or the first $MOVELOG command in a batch run is incorrect. |
|
Action:
|
Check whether a database entry exists for the specified user. If you use password protection, check whether the specified user has an entry in the user password table. |
E205 $MOVELOG: Database <db> not available
|
Explanation:
|
The current database for the $MOVELOG command is no longer available. |
|
Action:
|
Check your network. |
E209 $MOVELOG: Login cancelled by user
|
Explanation:
|
The first $MOVELOG command was cancelled by the user. |
E300 Client startup file <file> not found
|
Explanation:
|
The predialog file <file> specified in the STARTUP setting in the client start section of the initialization file cannot be found. |
|
Action:
|
Check if the path and file name of the predialog file have been specified correctly in the STARTUP setting. |
E310 No current database available
|
Explanation:
|
The current database is no longer available. |
|
Action:
|
Check your network. |
E311 Current database <dbname> is write protected
|
Explanation:
|
The current database <dbname> is write-protected. |
|
Action:
|
Check whether the database has been assigned to the server in write-protected mode, and change that assignment if necessary. Check the database assignment using $DB in your predialog file. If the database is not assigned in write-protected mode in the client predialog file, change the assignment to Update. |
E312 Database <dbname> cannot be opened for write
|
Explanation:
|
In your predialog file for the client, you attempted to assign in write mode ($DB <dbname> U) a database that is assigned to the server in write-protected mode. <dbname> is the logical name of the database. |
|
Action:
|
Change the assignment of the database to the server to Update if necessary. |
E313 Current database <dbname> cannot be closed
|
Explanation:
|
The command $DB <dbname> C cannot be applied to the current database. <dbname> is the logical name of the current database. |
E314 No procedure database defined
|
Explanation:
|
In your client predialog file, no database has been assigned as a procedure database. |
|
Action:
|
Assign at least one database as a procedure database. (You can use the command $DB <dbname> U P). |
E372 Server and client have incompatible version numbers
|
Explanation:
|
The server and client versions are mutually incompatible. Heed the statements about compatibility of client and server versions in the respective release notes. |
|
Action:
|
Use a client version that is compatible with your server version. For detailed information, see the respective release notes. |
E374 Number of client requests exceeds license
|
Explanation:
|
You have attempted to exceed the number of clients that you purchased as per your license agreement, or you have requested Rochade functions that are not covered by your license agreement. |
|
Action:
|
Contact ASG for a license that allows for more clients or for the required functionality. |
E375 $SEND: Stack size of %s in %s changed for existing object
|
Explanation:
|
In the class description of a derived class, new private data were introduced or private data were deleted. However, an object of the original class is still stored in memory. Rochade detects this modification when the class is reloaded. |
E376 $SEND: Stack size of <class> changed for existing object
|
Explanation:
|
In the class description, new private data were introduced or private data were deleted. However, an object of the original class is still stored in memory. Rochade detects this modification when the class is reloaded. |
E377 $SEND: Class description <class> changed for existing object
|
Explanation:
|
The class description was changed, but an object of the original class is still stored in memory. Rochade detects this modification when you attempt to create a new object of the class. |
E378 $SEND: Exception in external library <extlib>: <error>
|
Explanation:
|
An exception with error code <error> has occurred when the external library <extlib> was accessed. The reason is a programming error within your library leading to a memory protection violation. |
|
Action:
|
Make sure that in programming your functions and entry points you have correctly defined the respective memory areas. In addition, check if you have observed all the conventions for programming external libraries relevant for your operation system. |
E500 Incomplete path of editor file: $ED = <path>
|
Explanation:
|
In the variable $ED, an incomplete path has been specified for the editor file. In the message, the incomplete path is shown in <path>. Most likely, a relative path has been used, which is not allowed for the variable $ED. For more information on $ED, see the section about Rochade special variables in the ASG-Rochade Programmer’s Guide Volume 1. |
|
Action:
|
Complete the path in question and try again. |
E501 Values of $ED and $EDIT too large: <$ED string length> + <$EDIT string length> > max. (<maximum allowed value>)
|
Explanation:
|
The sum of the lengths of the strings in $ED and $EDIT exceeds the allowed maximum, which is also returned in parentheses. For more on $ED and $EDIT, see the section about Rochade special variables in the ASG-Rochade Programmer’s Guide Volume 1. |
|
Action:
|
Make sure that the total length of the strings in question stays within the allowed maximum. |
P001 No variables on the stack
|
Explanation:
|
There are no variables on the variables stack that could be displayed by the $SHOWSTK command. |
P002 Attribute <i_tp> <i_nm> <attr> has been written
|
Explanation:
|
The specified attribute has been written. |
P003 Attribute <i_tp> <i_nm> <attr> has been deleted
|
Explanation:
|
The specified attribute has been deleted. |
P004 Item <i_tp> <i_nm> has been deleted
|
Explanation:
|
The specified item has been deleted. |
P005 Item <i_tp> <i_nm> has been removed
|
Explanation:
|
The specified item has been physically removed from the database. |
P006 Attribute <i_tp> <i_nm> <attr> has been replaced
|
Explanation:
|
The specified attribute has been replaced. |
P007 Item <i_tp> <i_nm> has been renamed into <i_nm>
|
Explanation:
|
The specified item has been renamed. |
P008 Matrix table overflow occurred - report is incomplete
|
Explanation:
|
Matrix reports have yielded results that exceed the size of the report result table that was set using the $IQTAB command. |
|
Action:
|
Change the size of the report result table using the $IQTAB command. |
P010 Invalid format in User table <table>
|
Explanation:
|
One of your system tables (DOCTYPS, CHAPTYPS, or LINKTYPS) has an invalid format. |
P011 WARNING: Query delivers too many itemsP012 WARNING: Query result is incomplete
|
Explanation:
|
The report result is too big for the size of the report result table that was set using the $IQTAB command. |
|
Action:
|
Change the size of the report result table using the $IQTAB command. |
P013 Query table is empty
|
Explanation:
|
The report path table is empty. |
|
Action:
|
Check whether you filled the report path table using $DQCMD commands. |
P014 Overflow in the internal user class table
|
Explanation:
|
When evaluating the links between USER items in the course of loading the system tables ($MOVELOG), too many USER items were found (the maximum number of USER items in the user class table is 40). |
|
Action:
|
Try to simplify the user structure. |
P015 WARNING: NULL character replaced by space character while reading file
|
Explanation:
|
While reading a file (via $RSAM, $DOSAM, or $EDIT), NULL characters were encountered and converted to blanks. |
