Error Messages
CobolScript® Error Messages
T
he messages described in this appendix are produced when the CobolScript engine encounters an error while executing a CobolScript program. An error can be indicative of incorrect syntax, program inconsistencies, missing files, or improper system setup. The error messages listed below are in numerical order; where sequential error numbers have the same error message and description, the error number is provided as a range, and the errors are described in a single entry.
Error Number:
0000
Error Message:
"Usage: cobolscript.exe –b <filename> "
Description:
In order to build an executable from the command prompt using CobolScript AppMaker, you must specify a target filename to build.
Error Number:
0001
Error Message:
"Error opening file. File name may not exist: "
Description:
The file was not found. Attempts were made to open the file as named, and with extensions of .cbl, .cob, .CBL, .COB, but all of them failed. Check the spelling of the filename and verify that the file exists on your machine, in the specified path. If you are working on a Unix system, check the case of the filename as well.
Error Number:
0002
Error Message:
"Program file is empty: "
Description:
The specified program file exists but does not contain any CobolScript code.
Error Number:
0003
Error Message:
"Unrecognized CobolScript syntax."
Description:
An error has occurred that has stopped the execution of your program. This error is either a runtime error or a syntax error. Check the syntax of the line that caused the error, as well as the line immediately prior to it.
Error Number:
0004
Error Message:
"Stack overflow."
Description:
The maximum permitted CobolScript stack size has been exceeded. With this version of CobolScript, use fewer modules and avoid recursive calls where possible.
Error Number:
0005
Error Message:
"Line limit bypassed. This version of CobolScript has a line limit of: "
Description:
Your program has exceeded the maximum number of lines of code permitted per program for this version of CobolScript. The maximum is 32,767 lines.
Error Number:
0006
Error Message:
"Line limit bypassed. This version of CobolScript has a line limit of: "
Description:
Interactive mode error - Your program has exceeded the maximum number of lines of code permitted per program for this version of CobolScript. The maximum is 32,767 lines.
Error Number:
0007
Error Message:
"Nothing to run Use "load <filename>" to load a program. "
Description:
Interactive mode error - You are attempting to run a program in interactive mode, but no code has been loaded into the program buffer. Use the load command to load a CobolScript program before you try to run it.
Error Number:
0008
Error Message:
"Cannot display variable: "
Description:
Interactive mode error - You are trying to display a variable that has not been defined. Either it has not been created yet, or you have misspelled the variable name. In interactive mode, you must run a program before you can display its variables.
Error Number:
0009
Error Message:
"No program in buffer. Use load <filename> to load a program."
Description:
Interactive mode error - You are trying to list program code in interactive mode, but you have not loaded it into the program buffer yet. You must load a text file containing valid CobolScript code into the program buffer before you can list it.
Error Number:
0010, 0011
Error Message:
"No variables defined in program in buffer."
Description:
Interactive mode error - No variables have been defined yet. You must run a program before you can display its variables or its variable positions in interactive mode. The variables are defined as the CobolScript program is interpreted, so you must at least step through your variable definitions before you can display the variables.
Error Number:
0012
Error Message:
"No files defined in program in buffer."
Description:
Interactive mode error - No files are in memory yet. Because CobolScript is an interpreter, files will not be displayed until the appropriate FD statement is interpreted. You must run or step through a program before you can display its files.
Error Number:
0013
Error Message:
"No modules defined in program in buffer."
Description:
Interactive mode error - No modules have been defined yet. You must load a CobolScript program before you can display its modules. The code must have at least one module in order for it to be a valid program (modules are any paragraphs defined in your program).
Error Number:
0014-0017
Error Message:
"Error dumping variables to { dump.var | dump.mod | dump.lst | dump.pos }."
Description:
Interactive mode error - Make sure there is sufficient disk space to create the named dump file. Also, verify that the appropriate permissions are set to allow writing to the working directory.
Error Number:
0018
Error Message:
"Following file not found: "
Description:
Interactive mode error - The file was not found. Attempts were made to open the file as named, and with extensions of .cbl, .cob, .CBL, .COB, but all of them failed. Check the spelling of the filename and verify that the file exists on your machine, in the specified path.
Error Number:
0019
Error Message:
"Error saving to file: "
Description:
Interactive mode error - Cannot save file because the filename you have specified cannot be opened for writing. Check the permissions on the target directory and the available disk space on this machine, and make certain the file is not being accessed by another application.
Error Number:
0020
Error Message:
"Error writing to file: "
Description:
Interactive mode error - Cannot save to this file. The filename you have specified has been opened correctly, but an error has occurred while writing to that file. Check available disk space on this machine and permissions on the target directory, and make certain the file is not being accessed by another application.
Error Number:
0021-0025
Error Message:
"This line of code is too long: "
Description:
A single line of code in your CobolScript program has exceeded the maximum permissible length. Check for an unbalanced string (a missing ` symbol on either side of a string literal), a missing period in this or a prior sentence, or simply a line of code that is too large.
Error Number:
0026-0027
Error Message:
"Error loading copybook: "
Description:
A copybook could not be loaded. Make sure that the filename exists on the current machine, in the specified path. If you are working on a Unix system, check the case of the filename as well. Also, refer to any more specific errors issued in conjunction with this error message.
Error Number:
0028
Error Message:
"Program sentence is missing a terminating period. "
Description:
A program sentence is not correctly terminated with a period. A program sentence is a complete statement that is not embedded inside conditional or loop logic. All program sentences must end with a period.
Error Number:
0029
Error Message:
"Program sentence is missing a terminating period, END-IF, or END-PERFORM."
Description:
Either an IF statement is missing an END-IF, a PERFORM statement is missing an END-PERFORM, or a program sentence is missing a terminating period. Check the IF and PERFORM statements in your code for their ending keywords, and check for missing periods in the line causing the error and previous line(s).
Error Number:
0030
Error Message:
"Program line should not have a terminating period."
Description:
A code statement has a terminating period at the end of the line when it should not. Remove the period from the end of the line. Terminating periods are not permitted on lines that are embedded inside conditional or loop logic.
Error Number:
0031-0036
Error Message:
"Check for missing period. { Specific problem explanation }.”
Description:
The variable definition has incorrect syntax. Check for a missing period on this or the previous line, or see Chapter 3 for information on how to define variables.
Error Number:
0037, 0038
Error Message:
"String in line is not properly terminated."
Description:
A string in a line is not properly terminated with an ending string delimiter. Literal strings cannot extend across multiple lines.
Error Number:
0039
Error Message:
"This version of CobolScript does not permit more than two OCCURS clauses in a single group-level data item."
Description:
This version of CobolScript permits no more than two OCCURS clauses in one group- level data item. You must restructure your variable definitions so that this limit is not bypassed.
Error Number:
0040
Error Message:
"Nonnumeric variable not permitted in TIMES clause: "
Description:
The TIMES clause of OCCURS variables is only permitted to have a literal number or numeric variable index, but the existing index is non-numeric. Correct this by using a numeric literal or numeric variable qualifier instead.
Error Number:
0041, 0042
Error Message:
"Multilevel OCCURS clauses not permitted in CobolScript Standard Edition. Upgrade to Professional Edition for multilevel OCCURS support."
Description:
You have CobolScript Standard Edition, which does not permit multilevel OCCURS clauses (multidimensional arrays). Upgrade to CobolScript Professional Edition at https://www.cobolscript.com/cgi-bin/cobolscript.exe?catalog.cbl for multilevel OCCURS clause support.
Error Number:
0043
Error Message:
"Variable index argument to TIMES clause not found. Make certain variable is defined prior to this OCCURS definition."
Description:
The TIMES clause index variable is not defined. Define this variable, as a numeric, prior to defining the OCCURS variable that is causing this error.
Error Number:
0044
Error Message:
"Stack error in variable stack. Check your variable definition syntax."
Description:
CobolScript encountered an error while manipulating its internal variable stack. Correct any errors in your variable definition syntax to fix the problem; make certain that all variable definitions begin on a new line, with a positive integer value to begin the definition.
Error Number:
0045
Error Message:
"Stack overflow in variable stack. Reduce amount of nesting in gldi variables."
Description:
CobolScript ran out of variable stack space while pushing gldi nesting levels to its internal variable stack. Reduce the amount of nesting in your group-level data item variables.
Error Number:
0046
Error Message:
"The first variable defined in a program must be a top-level variable, with an outline level of 1."
Description:
The first variable defined in a program must have an outline level of 1. Modify the outline level of your first variable definition to remedy this.
Error Number:
0047
Error Message:
"Picture clause exceeds maximum token length permitted."
Description:
A picture clause must be no more than 80 characters in length. Change your picture clause to use shortened picture clause notation, such as PIC X(200), instead of
PIC XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.
Error Number:
0048
Error Message:
"Invalid variable definition syntax."
Description:
Check the syntax of your variable definition for any extra tokens or incorrect keyword usage.
Error Number:
0049-0051
Error Message:
"There was an error while setting the VALUE of this variable: "
Description:
There was a problem setting the VALUE of a variable in its definition. This may be because the picture clause of the variable and the value clause are incompatible. Alternatively, there may be an issue with the size of the VALUE you are setting.
Error Number:
0052
Error Message:
"To use PIC X(n), you must either specify a VALUE clause or use the implied PIC X(n) format."
Description:
The use of PIC X(n) requires that you specify a VALUE clause, or alternatively use the implied PIC X(n) format. Specify a value clause, or change the picture clause to the implied format by omitting everything from the variable definition except the variable outline level number and the literal value enclosed in string delimiters.
Error Number:
0053-0055
Error Message:
"Missing string delimiters or misspelled keyword in VALUE clause of variable definition."
Description:
This error is a result of specifying a VALUE clause in a variable definition that is not a literal keyword such as SPACE, SPACES, LINEFEED, TAB, etc., not a numeric literal, and not an alphanumeric literal enclosed in string delimiters ( `, the accent symbol, by default). You may not use variables in VALUE clauses; the value must either be a keyword or literal.
Error Number:
0056-0059
Error Message:
"Nonnumeric value in numeric variable's VALUE clause: "
Description:
Only numeric literals (i.e., numbers that are not enclosed by delimiters) are permitted in the VALUE clause of a numeric variable. Change the value clause to a literal number, not enclosed by delimiters.
Error Number:
0060, 0061
Error Message:
"VALUE keyword specified in variable definition but no VALUE clause exists."
Description:
Insert a value clause (i.e., an alphanumeric or numeric literal) as appropriate after the VALUE keyword.
Error Number:
0062, 0063
Error Message:
"Invalid variable definition syntax."
Description:
Some portion of this variable’s picture clause definition is incorrect. Check your syntax, paying attention to the picture clause definition.
Error Number:
0064
Error Message:
"Invalid alphanumeric picture clause: "
Description:
Some portion of this picture clause definition is incorrect. Correct any syntax errors.
Error Number:
0065
Error Message:
"Variable names must begin with a letter."
Description:
You cannot use numeric or special characters as the first character of a variable name. Modify your variable names to begin with letters only.
Error Number:
0066
Error Message:
"Maximum variable name length exceeded: "
Description:
The maximum length of a variable name has been exceeded. The maximum length is 80 characters. Reduce the number of characters in your variable name.
Error Number:
0067-0104
Error Message:
"Variable not defined: "
Description:
The named variable is not defined. Check the variable name against the variables you have defined in your program. If you are using an array element like variable-name(counter), make sure that counter is not zero, and is in the allowable range for that particular OCCURS clause.
Error Number:
0105
Error Message:
"A CGI variable in the submitting form does not have a matching CobolScript variable."
Description:
A CGI variable in the submitting form does not have a matching CobolScript variable. Create a matching variable in your program with the same name as the field name in the submitting form.
Error Number:
0106
Error Message:
"Invalid syntax in MOVE statement."
Description:
The syntax in the MOVE statement is incorrect. A MOVE statement must have at least 4 tokens, as in "MOVE <source> TO <target>". Verify the statement syntax, and verify that there are no unbalanced string terminators in the preceding line of code.
Error Number:
0107
Error Message:
"Cannot execute MOVE statement."
Description:
There was a problem executing this MOVE statement. Make certain that the source variable is a valid literal or variable, and that the target variable has been defined. It is possible that the MOVE failed because the picture clauses of the source and target variables were incompatible. If either the source or the target contains an array definition or a positional variable definition, make sure that it is properly defined prior to this statement.
Error Number:
0108
Error Message:
"Functions are not allowed as stand-alone arguments in MOVE statements."
Description:
Functions not allowed as stand-alone arguments in MOVE statements. If you wish to use functions or expressions as arguments in a variable assignment use the COMPUTE statement instead of MOVE.
Error Number:
0109
Error Message:
"Unrecognized or illegal source variable type."
Description:
The source variable of an illegal or unrecognized type for this MOVE statement. See the Language Reference for information on what source – target data type combinations are permissible in the MOVE statement.
Error Number:
0110
Error Message:
"Source or target argument in MOVE statement is too long."
Description:
The source or target argument in the MOVE statement is too long. It must be less than 180 characters.
Error Number:
0111
Error Message:
"Invalid syntax in INITIALIZE statement."
Description:
The INITIALIZE statement requires a minimum of 2 tokens to work properly; the first should be the keyword INITIALIZE, and the second should be a valid variable name.
Error Number:
0112
Error Message:
"INITIALIZE target variable not defined: "
Description:
The target variable name in the INITIALIZE statement was not properly defined. Verify that this variable is properly defined prior to this statement.
Error Number:
0113
Error Message:
"Invalid syntax in SET statement."
Description:
The SET command requires at least 4 tokens to work properly. See Language Reference for proper syntax of SET.
Error Number:
0114
Error Message:
"SET target variable not defined: "
Description:
The target variable name in the SET command could not be found in the variables in memory. Verify the name of this variable, and make certain it is defined prior to this statement.
Error Number:
0115
Error Message:
"Cannot execute SET statement."
Description:
There was a problem executing this SET statement. Make certain that the source variable is a valid literal or variable, and that the target variable has been defined. It is possible that the SET failed because the picture clauses of the source and target variables were incompatible. If either the source or the target contains an array definition or a positional variable definition, make sure that it is properly defined prior to this statement.
Error Number:
0116
Error Message:
"You have exceed the maximum allowable record length of 10k."
Description:
File records must be 10,000 bytes or less. You must split your file into multiple files if the current record size exceeds this limit.
Error Number:
0117
Error Message:
"Cannot close the following file: "
Description:
The file you are attempting to CLOSE has not been described in this program. Check the name of your file against the corresponding FD statement in your program.
Error Number:
0118
Error Message:
"Invalid syntax in CLOSE statement."
Description:
The CLOSE statement requires at least 2 tokens. See the Language Reference for proper syntax of the CLOSE statement.
Error Number:
0119
Error Message:
"Invalid syntax in OPEN statement."
Description:
At least 4 tokens are required for a properly defined OPEN statement. See the Language Reference for proper syntax of the OPEN statement.
Error Number:
0120
Error Message:
"The file you are attempting to open has not been described in an FD statement: "
Description:
You must describe all files used by a program in that program’s FD (File Description); check for an appropriate FD entry for the named file, and create it if it does not exist. The FD describes the filename and its record size to CobolScript which must be done before any I/O operations can take place on the file.
Error Number:
0121-0124
Error Message:
"Possible directory/file permission problem. This file could not be properly opened for
{ READING | UPDATING | WRITING | APPENDING } : "
Description:
The specified file could not be opened properly. The filename may be in use by another application, or may have too restrictive file permissions set. On Unix platforms, check the permissions on the directory and the named file; they must both allow writing by the user running the CobolScript program, and reading as well in the READING and APPENDING cases.
Error Number:
0125-0129
Error Message:
"You must open a file before you can { read from | write to | close | use POSITION on } it."
Description:
You are trying to perform a file operation on a file that has not yet been opened. Use the OPEN statement to open the file before performing any other file operations.
Error Number:
0130
Error Message:
"Cannot set buffering for file: "
Description:
There is a problem with the internal file buffering on your machine. If you get this error, raise a Problem Tracking Report (PTR) on the Deskware Registered User web site for further assistance.
Error Number:
0131
Error Message:
"Variables that are not alphanumerics or GLDIs cannot be used as file arguments: "
Description:
You used a non-alphanumeric, non-group item variable as a file argument in a file processing statement. Only alphanumeric variables and group-level data item variables can be used as filename arguments.
Error Number:
0132-0135
Error Message:
"Cannot find the FD for this file: "
Description:
The FD statement for the named file could not be found. Check that the FD statement exists. If it does, check for misspelling, or a wrong alphabetic case.
Error Number:
0136
Error Message:
"Invalid syntax in FD sentence."
Description:
A File Description sentence requires at least 6 tokens to be valid. See Chapter 3 for more on the syntax of FD.
Error Number:
0137
Error Message:
"Invalid syntax in READ statement."
Description:
At least 4 tokens are required for a properly defined READ statement. See the Language Reference for proper syntax of the READ statement.
Error Number:
0138
Error Message:
"Invalid target variable in READ statement: "
Description:
You have attempted to read a record from a file and move it into a variable that is either invalid or does not exist. Check to make sure that this variable has been properly defined prior to this statement.
Error Number:
0139
Error Message:
"End of file reached. Use AT END clause in READ statement to trap this error. File is: "
Description:
You have READ from a file and have encountered the end of the file. Avoid this error by placing an AT END MOVE <literal|var> TO <var> clause at the end of the READ statement. This will trap this error and set a variable to indicate the end of file has been reached. See the Language Reference for a full description of the READ statement.
Error Number:
0140
Error Message:
"Incorrect CobolScript syntax following AT END clause in READ statement."
Description:
A complete and valid CobolScript statement must follow the AT END clause in a READ statement.
Error Number:
0141
Error Message:
"Missing imperative following AT END clause in READ statement."
Description:
The AT END clause in this READ statement is missing an imperative statement after it. A complete and valid CobolScript statement must follow the AT END clause.
Error Number:
0142
Error Message:
"You are attempting to read data that contains a decimal into a variable with an implied decimal format. "
Description:
This error occurs when you are trying to read a field of data that contains a explicit decimal into a variable that has an implied decimal (“V”) format. If your numeric data for this field in the record contains a decimal, you should use a decimal format for the variable that is to receive this data. This error can also occur when you are moving a group level data item to another group level data item and there is a mismatch of implied decimal and explicit decimal variables.
Error Number:
0143
Error Message:
"The file you are attempting to write to has not been described in an FD statement: "
Description:
You must describe all files used by a program in that program’s FD (File Description); check for an appropriate FD entry for the named file, and create it if it does not exist. The FD describes the filename and its record size to CobolScript which must be done before any I/O operations can take place on the file.
Error Number:
0144-0150
Error Message:
"{ Write | Rewrite | POSITION statement } error. Possible directory/file permission problem, disk space problem, or file has not been opened: "
Description:
An error occurred while attempting to write to or position a file. The file may not have been opened with the OPEN statement, the permissions in the directory where the file exists may not be properly set to permit writing, or the disk may be full.
Error Number:
0151, 0152
Error Message:
"Error writing to file. File may not have been opened properly."
Description:
An error has occurred while trying to write data to a file. Verify that the permissions in the directory where the file exists allow writing by the user running the program. Also make certain that the file you are attempting to write to has been opened.
Error Number:
0153
Error Message:
"Rewrite error. Check data file record length against byte size declared in FD statement for: "
Description:
When using the REWRITE statement, the record byte size that you specify in the FD statement for the file must exactly match the actual physical record length of the file records. Determine the actual record length of your file record and use this value in the BYTE clause of your FD statement.
Error Number:
0154-0157
Error Message:
"POSITION offset argument is invalid. It should be a numeric integer variable or value: "
Description:
The offset argument to a position statement must be either an integer numeric literal, or a numeric variable containing an integer value. If you are specifying a variable as an argument, make certain that the variable is defined with a numeric picture clause, and that it does not have any post-decimal component.
Error Number:
0158, 0159
Error Message:
"POSITION offset argument is causing an out of range value for the record position: "
Description:
The argument that you have specified to the POSITION statement has a value that is pointing to a position that is either before the beginning of the file or after the end of the file.
Error Number:
0160
Error Message:
"POSITION statement error. Check data file record length against byte size declared in FD statement for: "
Description:
When using the POSITION statement, the record byte size that you specify in the FD statement for the file must exactly match the actual physical record length of the file records. Determine the actual record length of your file record and use this value in the BYTE clause of your FD statement.
Error Number:
0161
Error Message:
"Cannot open file: "
Description:
The specified file argument to DISPLAYFILE could not be opened. The filename may not exist as named on your machine (a file must already exist on your machine in order for it to be successfully opened for reading). On Unix platforms, check the permissions on the directory and the named file; they must both allow reading by the user running the CobolScript program.
Error Number:
0162
Error Message:
"Error in internal DISPLAY of: "
Description:
This error applies to an internal Deskware debugging command. It should not arise in your normal programming.
Error Number:
0163, 0164
Error Message:
"Error in { DISPLAY | DISPLAYLF } of: "
Description:
You have attempted to DISPLAY or DISPLAYLF an argument to standard output, but it failed. If the argument is a variable name or contains a variable name, check to see if this variable has been properly defined prior to the display statement.
Error Number:
0165
Error Message:
"No arguments specified."
Description:
No arguments have been specified in this DISPLAY statement. There must be at least one argument to DISPLAY.
Error Number:
0166
Error Message:
"Line too long in DISPLAY statement."
Description:
You have exceeded the maximum line length of 500 characters in this DISPLAY statement. Shorten this DISPLAY by placing a portion of the argument on another line in a new DISPLAY statement.
Error Number:
0167, 0168
Error Message:
"Missing ampersand or string delimiter in DISPLAY of literal."
Description:
A error in the DISPLAY of a literal has occurred. Check for missing string delimiters, or missing ampersands (&) between multiple DISPLAY arguments.
Error Number:
0169-0191
Error Message:
" TCP/IP is not currently available."
Description:
You are attempting to use a command that requires TCP/IP, but the TCP/IP protocol is not currently available on your machine. Make certain that you have an open internet or network connection utilizing TCP/IP before using this command.
Error Number:
0192-0194
Error Message:
"{ FTPCLOSE | FTPBINARY | FTPASCII } failed."
Description:
An FTP statement has failed. Your connection may have timed out prior to the execution of the statement.
Error Number:
0195
Error Message:
"The FTPCONNECT statement has failed to connect to the following server name: "
Description:
An attempt to connect to an FTP server has failed. Make certain that the named remote server is available, and is running as an FTP server. Also, if you are using variable names to contain your parameters, make sure they have been properly defined prior to this statement.
Error Number:
0196
Error Message:
"The FTPCD statement failed to change directories to the following path: "
Description:
The FTPCD command has failed. Verify that the named path exists on the remote server. If you are using a variable to hold the directory name, make certain it has been properly defined prior to this statement. It is also possible that the FTP connection timed out before the FTPCD statement could be successfully executed.
Error Number:
0197
Error Message:
"The FTPGET statement failed for the file: "
Description:
The FTPGET command has failed for the named file. Verify that the file exists on the remote server. Also, if you are using a variable to hold the file name, make certain it has been properly defined prior to this statement. It is also possible that the FTP connection timed out before the FTPGET command could be successfully executed.
Error Number:
0198
Error Message:
"The FTPPUT statement failed for the file: "
Description:
The FTPPUT command has failed. Verify that the local file exists in the specified path. If you are using a variable to hold the file name, make certain it has been properly defined prior to this statement. It is also possible that the FTP connection timed out before the FTPPUT command could be successfully executed.
Error Number:
0199-201
Error Message:
"The { SENDMAIL | GETMAILCOUNT | GETMAIL } statement has failed."
Description:
A mail command that you are trying to execute has failed. If you are using variables to hold the contents of your parameters, verify that they are properly defined prior to this statement. Verify that the userid and password are valid for the SMTP server you are trying to connect to, and verify that you can establish connectivity to the SMTP server from your local machine, using ping or a similar operating system command.
Note: Some firewalls will prevent you from connecting and receiving data from a SMTP server. Also, some SMTP servers will not allow you to forward mail unless you have a valid userid and password.
Error Number:
0202
Error Message:
"The GETWEBPAGE statement failed."
Description:
The GETWEBPAGE command you are trying to execute has failed. If you are using variables to hold the contents of your parameters, verify that they are properly defined prior to this statement. Verify that the URL you are trying to GET is valid. Also, verify that you can establish connectivity to the remote server.
Error Number:
0203, 204
Error Message:
"{ CREATESOCKET | CLOSESOCKET } failed for socket: "
Description:
A socket command has failed. Check the contents of the TCP/IP return code variables for further information.
Error Number:
0205-0210
Error Message:
"Could not { use SHUTDOWNSOCKET on | BINDSOCKET to | LISTENTOSOCKET on
| ACCEPTFROMSOCKET on | SENDSOCKET to | RECEIVESOCKET from } socket: "
Description:
A socket command has failed. Check the contents of the TCP/IP return code variables for further information.
Error Number:
0211
Error Message:
"The GETENV statement failed to get: "
Description:
If you are using a variable name as a parameter, verify that is has been properly defined prior to this statement.
Error Number:
0212
Error Message:
"Syntax error in GETENV statement."
Description:
Your GETENV statement syntax is incorrect. See the Language Reference for the correct syntax.
Error Number:
0213, 0214
Error Message:
"There was an error getting the { hostname | host by name } : "
Description:
There was a problem getting the hostname or host by name. If you are using a variable to store the hostname, make sure that it is properly defined prior to this statement.
Error Number:
0215
Error Message:
"There was an error with GETTIMEFROMSERVER."
Description:
There was an error getting the time from a server. If you are using a variable to store the hostname, make sure that it is properly defined prior to this statement. Also, make certain that the machine has a time daemon running on it – if it doesn’t, you will not be able to get the time from it.
Error Number:
0216-0222
Error Message:
"{ TCPIP-HOSTENT-ADDRESS-TYPE | TCPIP-HOSTENT-ADDRESS-LENGTH |
TCPIP-HOSTENT-ADDRESS | TCPIP-HOSTENT-ALIAS |
TCPIP-HOSTENT-HOSTNAME | TCPIP-RETURN-CODE | TCPIP-RETURN-MESSAGE } not defined."
Description:
You attempted to use an internetworking command, but the named variable was not properly defined in your program. This variable must be defined when this command is used. See the Language Reference for the internetworking command you are attempting to implement.
Error Number:
0223-0232
Error Message:
"Maximum number of sockets exceeded."
Description:
Your socket command has exceeded the maximum number of sockets allowed in this version of CobolScript. The maximum number of sockets is 20.
Error Number:
0233
Error Message:
"Shutdown method must be 0,1, or 2."
Description:
SHUTDOWNSOCKET requires that a shutdown method equal to 0, 1, or 2 be specified.
Error Number:
0234
Error Message:
"SLEEP statement failed. Argument was : "
Description:
This error message should not be encountered with this version of CobolScript
Error Number:
0235-0238
Error Message:
"Module not defined: "
Description:
The named module could not be found, probably because of a misspelling. Verify that the module named references a valid module name.
Error Number:
0239,0240
Error Message:
"This PERFORM statement is missing an UNTIL keyword."
Description:
A PEFORM statement was found to be missing the UNTIL keyword in a case where UNTIL was required. See the Language Reference for proper syntax of PERFORM .. UNTIL.
Error Number:
0241,0242
Error Message:
"Missing UNTIL keyword in this PERFORM VARYING."
Description:
A PEFORM .. VARYING statement was found to be missing the UNTIL keyword. See the Language Reference for proper syntax of PERFORM .. VARYING.
Error Number:
0243-0246
Error Message:
"Invalid syntax in { inline PERFORM | PERFORM VARYING | PERFORM UNTIL } statement."
Description:
A PERFORM statement was found to have too few tokens to be valid. See the Language Reference for proper syntax of the type of PERFORM you are attempting to implement.
Error Number:
0247-0250
Error Message:
"The PERFORM VARYING statement must contain a { FROM | BY } keyword and value."
Description:
The FROM and BY keywords and values are required in PERFORM .. VARYING; the FROM value specifies the initial value for the varying variable, while the BY value specifies the quantity by which the varying variable will be incremented.
Error Number:
0251,0252
Error Message:
"The VARYING variable is not defined as numeric: "
Description:
The variable name after the VARYING keyword in the PERFORM .. VARYING statement was not defined with a numeric picture clause. Make sure that it is defined as a numeric prior to this statement.
Error Number:
0253, 0254
Error Message:
"Cannot initialize VARYING variable to the starting value: "
Description:
The variable name after the VARYING keyword in the PERFORM .. VARYING statement could not be initialized to the starting value (value after FROM keyword). Make sure that the VARYING variable is defined as a numeric, and that the FROM value is also a valid numeric.
Error Number:
0255, 0256
Error Message:
"Inline { PERFORM | PERFORM VARYING } must have code statements between the PERFORM and END-PERFORM."
Description:
In your version of CobolScript, inline PERFORMs must have statements between the PERFORM and END-PERFORM. Modify your code accordingly.
Error Number:
0257
Error Message:
"IF or PERFORM statement missing END-IF or END-PERFORM keyword."
Description:
Either an IF statement is missing an END-IF, or a PERFORM statement is missing an END-PERFORM. Check the IF and PERFORM statements in your code for their ending keywords.
Error Number:
0258-0261
Error Message:
"Missing END-IF for IF clause."
Description:
An END-IF is missing for an IF statement. Insert the END-IF.
Error Number:
0262-0264
Error Message:
"{ ELSIF | ELSE | END-IF } without initial IF clause."
Description:
The named keyword is not preceded by an IF clause. This keyword must succeed an IF clause for the syntax to be correct.
Error Number:
0265
Error Message:
"An ACCEPT statement has failed."
Description:
The ACCEPT statement has failed, possibly because one of the receiving variables is not defined. Alternatively, the syntax is incorrect. See the Language Reference for proper syntax of the ACCEPT statement.
Error Number:
0266
Error Message:
"The FROM keyword is missing from this ACCEPT statement."
Description:
The FROM keyword was missing in the ACCEPT statement. See the Language Reference for the proper syntax of the ACCEPT statement.
Error Number:
0267
Error Message:
"Error ACCEPTing standard input into: "
Description:
There was an error accepting standard input into the named target variable. Check the picture type and length of the variable, and make certain it is properly defined.
Error Number:
0268
Error Message:
"An error occurred while ACCEPTing CGI data from the web server."
Description:
An ACCEPT of CGI data from a web server failed. Make certain that there is data to ACCEPT; this can be verified by accepting and examining the environmental variable CONTENT_LENGTH; if CONTENT_LENGTH is populated with zero, then there is no data to accept from the web server.
Error Number:
0269
Error Message:
"Syntax error in ACCEPT statement."
Description:
A syntax error was found in the ACCEPT statement. See the Language Reference for the proper syntax of the ACCEPT statement.
Error Number:
0270
Error Message:
"Third parameter to GETBANNER must be a group-level data item: "
Description:
The third parameter of the GETBANNER function must be a 01 level group-level data item.
Error Number:
0271
Error Message:
"GETBANNER requires a group-level data item with 8 elementary data items as the target variable."
Description:
The GETBANNER command requires, as the target variable, a group-level data item with eight elementary data items defined as subvariables.
Error Number:
0272, 0273
Error Message:
"Unable to allocate memory required to { print | create } calendar."
Description:
There is not sufficient memory available when this program runs to successfully print or create the calendar. Either reduce the size of your program or the number of variables declared in your program, or use a computer with more memory.
Error Number:
0274, 0275
Error Message:
"{ CALENDAR | GETCALENDAR } year data type mismatch. Year input must be
numeric: "
Description:
There is a data type mismatch - the year parameter to this statement must be a numeric literal, or a variable defined with a numeric picture clause. See the Language Reference for the proper syntax of the CALENDAR or GETCALENDAR statement.
Error Number:
0276, 0277
Error Message:
"{ CALENDAR | GETCALENDAR } month data type mismatch. Month input must be numeric: "
Description:
There is a data type mismatch - the month parameter to this statement must be a numeric literal, or a variable defined with a numeric picture clause. See the Language Reference for the proper syntax of the CALENDAR or GETCALENDAR statement.
Error Number:
0278, 0279
Error Message:
"Range error in month input to { CALENDAR | GETCALENDAR } statement. Following input month does not fall within range of 1-12: "
Description:
The month input to this statement must be a numeric value in the range 1 to 12 (January to December).
Error Number:
0280, 0281
Error Message:
"{ CALENDAR | GETCALENDAR } year must be greater than zero, but following input year is not greater than zero: "
Description:
Range error: The input year to this statement must be greater than zero.
Error Number:
0282, 0283
Error Message:
"{ CALENDAR | GETCALENDAR } statement does not support pre-Julian calendar dates (dates prior to August 1752)."
Description:
This statement does not handle pre-Julian dates, but your input is pre-Julian. Only dates after August 1752 will be correctly processed.
Error Number:
0284
Error Message:
"Third parameter to GETCALENDAR must be a group-level data item: "
Description:
The third parameter of the GETCALENDAR function must be a 01 level group-level data item with eight elementary data item subvariables.
Error Number:
0285
Error Message:
"GETCALENDAR requires a group-level data item with 8 elementary data items as the target variable."
Description:
The GETCALENDAR statement requires, as the target variable, a group-level data item with eight elementary data items defined as subvariables.
Error Number:
0286
Error Message:
"An argument to the EXECUTE statement contains an undefined variable or a literal that is missing delimiters."
Description:
Check the variable that is the statement argument for the EXECUTE statement. There is a problem with one of the underlying variable or literal constructs of your dynamic statement variable.
Error Number:
0287
Error Message:
"The syntax of the statement being executed is incorrect."
Description:
Check the variable that is the statement argument for the EXECUTE statement. There is a problem with the statement syntax.
Error Number:
0288
Error Message:
"Missing argument in EXECUTE statement."
Description:
Check the syntax of your EXECUTE statement and specify an appropriate argument.
Error Number:
0289
Error Message:
"Invalid CobolScript statement. This syntax is unsupported."
Description:
You have entered an invalid CobolScript statement. Check your syntax and try again.
Error Number:
0290-0294
Error Message:
"A { COMPUTE | ADD | SUBTRACT | MULTIPLY | DIVIDE } statement has failed."
Description:
Verify that the variables in your math statement are properly defined, and make certain that any expressions and function calls are valid.
Error Number:
0295
Error Message:
"Error encountered while evaluating COMPUTE expression."
Description:
Make sure that the variables you are using in the COMPUTE statement are properly defined, and that the expression has valid syntax.
Error Number:
0296
Error Message:
"Alphanumeric literals are not permitted inside computational statements."
Description:
String literals are not permitted inside computational statements; computational statements are used for mathematical operations only. To manipulate strings, use the MOVE statement.
Error Number:
0297
Error Message:
"Incorrect use of ROUNDED keyword in COMPUTE statement."
Description:
The ROUNDED keyword is used incorrectly in a COMPUTE statement. See the Language Reference entry for the COMPUTE statement for information on proper use of the ROUNDED keyword.
Error Number:
0298
Error Message:
"Invalid or missing variable name after REMAINDER keyword."
Description:
You have used the REMAINDER keyword in a DIVIDE statement, but have not specified a valid variable name to accept the remainder information. See the Language Reference entry for the DIVIDE statement for information on proper use of the REMAINDER clause.
Error Number:
0299, 0300
Error Message:
"Syntax error in REMAINDER clause in DIVIDE statement."
Description:
You have used the REMAINDER keyword in a DIVIDE statement, but the syntax is incorrect. See the Language Reference entry for the DIVIDE statement for information on proper use of the REMAINDER clause.
Error Number:
0301
Error Message:
"A GIVING clause must accompany DIVIDE statements that use the BY keyword."
Description:
You have used the BY keyword in a DIVIDE statement, but have failed to specify a GIVING clause. See the Language Reference entry for the DIVIDE statement for information on proper syntax.
Error Number:
0302
Error Message:
"Input length issue. Your expression must be smaller."
Description:
In this version of CobolScript expressions must be less than 180 characters total; the expression down into multiple statements, or make it less than 180 characters.
Error Number:
0303
Error Message:
"Expression expected in statement."
Description:
An expression was expected in the statement, but none was found. Check for the proper syntax of your statement in the Language Reference.
Error Number:
0304-0309
Error Message:
"Syntax error in expression."
Description:
Check the syntax of any expressions in this statement. If you are displaying an expression, make certain you separate multiple arguments with an ampersand. Refer to Chapter 3, CobolScript Language Constructs, for more information on expression syntax
Error Number:
0310, 0311
Error Message:
"Expressions are not allowed in this statement’s syntax."
Description:
Expressions are not allowed in positional string referencing for this particular statement. You must first set a variable equal to the expression of interest using a COMPUTE statement, then substitute this variable for the expression in the positional string reference.
Error Number:
0312, 0313
Error Message:
"Maximum individual argument length exceeded in expression."
Description:
The maximum individual argument length in an expression has been exceeded. Insert spaces between expression elements to reduce argument length. The maximum individual argument length is 80 characters.
Error Number:
0314-0316
Error Message:
"Missing parenthesis in expression."
Description:
A parenthesis was missing from an expression. Insert the missing parenthesis.
Error Number:
0317
Error Message:
"Operator encountered without appropriate operand in expression."
Description:
An operator (+, -, /, *, %, etc.) was encountered in an expression but there was no target operand. In other words, the operator was a dangling operator. Insert the operand in the expression.
Error Number:
0318
Error Message:
"Non-numeric variables are not permitted here. Contents of this variable are non-numeric:"
Description:
You are attempting to use a non-numeric variable in a computational statement. Revise your statement to only use numeric variables.
Error Number:
0319
Error Message:
"Misplaced comma in expression."
Description:
You have placed a comma inside an expression when it should not be there. Commas are only valid in expressions as function parameter separators or occurs clause argument separators (Professional Edition only). Remove the misplaced comma.
Error Number:
0320
Error Message:
"Invalid terminating character in expression."
Description:
The terminating character in the expression is an operator or other inappropriate character. Check your expression syntax.
Error Number:
0321
Error Message:
"OCCURS clause group items are not allowed in expressions."
Description:
OCCURS clause group items are not allowed in expressions. Rewrite this expression using an elementary data item. If necessary, substitute an elementary data item directly for the OCCURS clause group item.
Error Number:
0322
Error Message:
"Group-level data items are not allowed in expressions."
Description:
Group-level data items are not permitted in expressions, since their value is not strictly numeric, but is comprised of other variables Modify the expression or condition to use only numeric literals and variables.
Error Number:
0323
Error Message:
"Missing parenthesis in function call."
Description:
A parenthesis is missing from a function call. Add the missing parenthesis.
Error Number:
0324
Error Message:
"Function called with wrong number of parameters. Function is: "
Description:
The function was called with the wrong number of parameters. Check the function syntax in the Function Reference.
Error Number:
0325
Error Message:
"Too many parameters in call to function."
Description:
The function was called with the wrong number of parameters. Check the function syntax in the Function Reference.
Error Number:
0326
Error Message:
"Undefined function."
Description:
A function is undefined. Check the spelling of your function name.
Error Number:
0327
Error Message:
"In function: "
Description:
Parameter error in function. Specific error messages always follow this message.
Error Number:
0328, 0329
Error Message:
"Division by zero is not permitted."
Description:
Your are attempting to perform division with a zero-valued divisor. Correct the expression so that division by zero does not occur.
Error Number:
0330
Error Message:
"Raising negative numbers to fractional powers is not permitted."
Description:
You are attempting to raise a negative number to the power of a fractional number. Even roots of negative numbers are imaginary numbers, which are not supported; however, because of the difficulty in determining whether a root is even or odd, raising negative numbers to any fractional power is prohibited. Modify the expression so that no negative numbers are raised to fractional powers.
Error Number:
0331
Error Message:
"Empty argument in reference modification or array variable."
Description:
No argument was specified in an array or reference modification. Insert a valid index in your positional string reference or array.
Error Number:
0332
Error Message:
"Empty second argument in reference modification."
Description:
The positional string reference was missing the second argument. Insert a valid numeric argument in your positional string reference or array.
Error Number:
0333
Error Message:
"Invalid syntax in reference modification."
Description:
You have specified more than two arguments or more than one separating colon in a reference modification argument. Proper reference modification syntax is of the form:
variable-name(start-pos:end-pos)
Error Number:
0334, 0335
Error Message:
"Incorrect syntax inside reference modification or array variable. Value of argument must be a positive integer: "
Description:
All arguments to arrays and positional string references must be positive (strictly greater than zero) integers. Correct the argument that is not a positive integer.
Error Number:
0336
Error Message:
"Reference modification is not permitted with numeric variables or group-level data items."
Description:
Positional string referencing is not permitted with numeric variables or group-level data items. If you are working with a numeric or group-level data item variable and wish to isolate certain component characters or digits, move the variable to a group-level data item with the appropriate elementary items.
Error Number:
0337
Error Message:
"Internal error in variable processing."
Description:
Internal error in variable processing. This error should not be encountered in the course of normal programming.
Error Number:
0338-0341
Error Message:
"Internal error in processing of { ADD | SUBTRACT | MULTIPLY | DIVIDE } statement."
Description:
Internal error with math statement processing. This error should not be encountered in the course of normal programming.
Error Number:
0342-0344
Error Message:
"Internal error - stack space violation."
Description:
The expression stack limit was violated. Break your expression into multiple assignment statements with smaller component expressions.
Error Number:
0345-0348
Error Message:
"Internal error – explanatory text."
Description:
Internal error with expression evaluation. These errors should not be encountered in the course of normal programming.
Error Number:
0349-0352
Error Message:
"LinkMaker SQL { FETCH | CLOSE | OPEN } error: Cursor is not declared: "
Description:
Before you can use an SQL FETCH, CLOSE, or OPEN statement, your cursor must be declared using an SQL DECLARE.
Error Number:
0353
Error Message:
"LinkMaker SQL FETCH error: ABSOLUTE row number must be a positive integer. "
Description:
When using FETCH ABSOLUTE, the row number value following the ABSOLUTE keyword must be a positive integer, but the row number value that you specified was not.
Error Number:
0354
Error Message:
"LinkMaker SQL FETCH error: Invalid extended fetch type."
Description:
The extended fetch type (the keyword that follows FETCH in an extended fetch) is invalid. Valid extended fetch types are FETCH NEXT, FETCH PRIOR, FETCH FIRST, FETCH LAST, FETCH ABSOLUTE, and FETCH RELATIVE.
Error Number:
0355
Error Message:
"LinkMaker error: You have exceeded the maximum number of allowable cursors."
Description:
The maximum number of allowed cursors open at one time is 100. Reduce the number of open cursors in your program.
Error Number:
0356
Error Message:
"LinkMaker error: Data source returned an invalid column datatype."
Description:
The data source that you have established a connection with has returned a column datatype that is not a valid ODBC column datatype. Valid ODBC column datatypes are CHAR, VARCHAR, SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL, FLOAT, AND DOUBLE. Your database’s ODBC driver must convert any native database datatypes to these ODBC datatypes, so this error indicates that a bug exists in your ODBC driver. Contact your ODBC driver vendor to report the problem.
Error Number:
0357
Error Message:
"LinkMaker error: SQL host variable not found: "
Description:
A host (receiving) variable was not defined. Host variables must be defined in your CobolScript program using normal variable definition syntax before being used in a LinkMaker SQL statement.
Error Number:
0358
Error Message:
"LinkMaker DBOPEN error: Return code variable not found: "
Description:
The return code variable for your DBOPEN statement was not defined.
Error Number:
0359
Error Message:
"LinkMaker DBCLOSE error: Return code variable not found: "
Description:
The return code variable for your DBCLOSE statement was not defined.
Error Number:
0360
Error Message:
"LinkMaker error: You must be connected to a data source before executing SQL statements."
Description:
You attempted to execute a LinkMaker SQL statement, but there is not data source connection established. Establish a connection with your data source first by using DBOPEN.
Error Number:
0361
Error Message:
"LinkMaker DBOPEN error: Data source name variable is not defined: "
Description:
The data source name specified in the OPENDB statement is not a validly defined variable. If you wish to specify a literal value instead of a variable, enclose the literal in string delimiters.
Error Number:
0362
Error Message:
"LinkMaker DBOPEN error: Data source user id variable is not defined: "
Description:
The data source user id specified in the OPENDB statement is not a validly defined variable. If you wish to specify a literal value instead of a variable, enclose the literal in string delimiters.
Error Number:
0363
Error Message:
"LinkMaker DBOPEN error: Data source password variable is not defined: "
Description:
The data source password specified in the OPENDB statement is not a validly defined variable. If you wish to specify a literal value instead of a variable, enclose the literal in string delimiters.
Error Number:
0364
Error Message:
"LinkMaker DBOPEN error: Return code must be a variable instead of a literal: "
Description:
You have specified a literal to accept the return code value, but the return code must be a previously defined variable.
Error Number:
0365
Error Message:
"LinkMaker DBCLOSE error: Return code must be a variable instead of a literal: "
Description:
You have specified a literal to accept the return code value, but the return code must be a previously defined variable.
Error Number:
0366
Error Message:
"LinkMaker error: Unable to establish connection with data source. SQLERRORMESSAGE is: "
Description:
There was a problem while attempting to connect with the data source. See the SQLERRORMESSAGE text following this error message for further details.
Error Number:
0367
Error Message:
"REPLICA variable's value parent is not already defined: "
Description:
A variable must be defined before a REPLICA of that variable can be defined. Check to make sure that the variable you are making a REPLICA of has been defined. Also, check to make sure that the spelling of the REPLICA variable and its parent are the same.
Error Number:
0368
Error Message:
"REPLICA variable does not have the same level number as its value parent."
Description:
The contents of the value parent cannot be properly duplicated if it has a different level number than the REPLICA variable.
Error Number:
0369
Error Message:
"REPLICA variable's value parent cannot be a group level data item."
Description:
The value parent of a REPLICA variable cannot be a group level data item. Only elementary data items can be used as value parents.
Error Number:
0370
Error Message:
"REPLICA variable cannot be a group level data item: "
Description:
A REPLICA variable must be defined as an elementary data item.
Error Number:
0371
Error Message:
"An argument to the CALL statement contains an undefined variable or a literal that is missing delimiters."
Description:
One of the arguments of the CALL statement is either an undefined variable, or a literal that is not enclosed in string delimiters. If it is a variable, verify that it has been defined and that you have used the correct spelling in the statement. If it is a literal, make sure that you put a string delimiter before and after the literal.
Error Number:
0372
Error Message:
"The syntax of the statement being called is incorrect."
Description:
See Appendix A for a description of the CALL command. You may use multiple arguments for the CALL statement. These arguments may be literals, keywords or variables. Verify that your literals are properly delimited and that your variables have been defined.
Error Number:
0373
Error Message:
"Missing argument in CALL statement."
Description:
The CALL statement requires at least one literal or keyword argument. See Appendix A for a description of the CALL command.
Error Number:
0374
Error Message:
"Variable not defined: "
Description:
The named variable is not defined. Check the variable name against the variables you have defined in your program.
Error Number:
0375
Error Message:
"This variable argument to the BYTES clause must be defined as a numeric: "
Description:
You are attempting to define the byte size of a record with a variable that is not defined as a numeric data type. Change the definition so that it is a numeric data type.
Error Number:
0376
Error Message:
"BYTES clause argument cannot have a value of zero."
Description:
You cannot specify a BYTES clause argument that has a value of zero. If you need to create data files with 0 bytes in them, use an arbitrary BYTES clause size (For example: 80) and then OPEN and CLOSE the file for WRITING. A file of zero length will be created.
Error Number:
0377, 0378
Error Message:
"The maximum number of permitted files has been exceeded. {Explanatory text}."
Description:
You have exceeded the maximum number of permitted files for your edition of CobolScript. If you have CobolScript Standard Edition, you should upgrade to the Professional Edition at https://www.cobolscript.com/cgi-bin/cobolscript.exe?catalog.cbl for support for greater numbers of variables. If you have the Professional Edition and you require additional variable support, call the number provided in the error message to order a custom edition of CobolScript with enhanced file support.
Error Number:
0379-0386
Error Message:
"The maximum number of allowed variable declarations has been exceeded. {Custom text}."
Description:
You have exceeded the maximum number of permitted variables for your edition of CobolScript. If you have CobolScript Standard Edition, you should upgrade to the Professional Edition at https://www.cobolscript.com/cgi-bin/cobolscript.exe?catalog.cbl for support for greater numbers of variables. If you have the Professional Edition and you require additional variable support, call the number provided in the error message to order a custom edition of CobolScript with enhanced variable support.
Error Number:
0387
Error Message:
“The EXECUTE recursive stack limit has been exceeded. Reduce the number of recursive EXECUTE calls in your program."
Description:
You have exceeded the maximum number of recursive calls using the EXECUTE statement. You must reduce the number of recursive calls in this particular EXECUTE recursion.
Error Number:
0388-420
Error Message:
“Variable not defined: "
Description:
The named variable is not defined. Check the variable name against the variables you have defined in your program. If you are using an array element like variable-name(counter), make sure that counter is not zero, and is in the allowable range for that particular OCCURS clause.
Error Number:
0421
Error Message:
"Cannot open file: "
Description:
The specified file argument to DISPLAYASCIIFILE could not be opened. The filename may not exist as named on your machine (a file must already exist on your machine in order for it to be successfully opened for reading). On Unix platforms, check the permissions on the directory and the named file; they must both allow reading by the user running the CobolScript program.
Error Number:
0422
Error Message:
“The argument of the GETHOSTNAME command must be a variable."
Description:
You must specify an alphanumeric variable (not a literal or numeric variable) to receive the value that is returned from the GETHOSTNAME command. The value returned will be the host name of your machine.
Error Number:
0423
Error Message:
“The email number must be a variable. "
Description:
You must specify a numeric variable (not a literal) that will receive the email number when you use the GETMAILCOUNT command.
Error Number:
0424
Error Message:
“The argument to the INITIALIZE command cannot be a literal."
Description:
You cannot use a literal as an argument to the INITIALIZE command. Specify a variable that is to be initialized as the INITIALIZE argument.
Error Number:
0425
Error Message:
"The last argument to GETBANNER cannot be a literal."
Description:
The last argument to the GETBANNER statement must be a group item variable with eight elementary item subvariables, rather than a literal or an elementary item. Once populated, it will contain the contents of a Unix-style banner. See the GETBANNER entry in Appendix A for more information about this command.
Error Number:
0426
Error Message:
"Non-numeric data and/or group items are not permitted in this statement."
Description:
Non-numeric literals and group item variables are not permitted in expressions, since their value is not strictly numeric, but is comprised of other variables Modify the expression or condition to use only numeric variables and literals.
Error Number:
0427
Error Message:
"This group item variable is too large to evaluate inside this statement: "
Description:
Group item variables must be less than 2000 bytes when they are tested or evaluated inside a condition. The group item variable that you are testing exceeds 2000 bytes in length.
Error Number:
0428
Error Message:
"Group item variables are not permitted in this type of expression."
Description:
Group item variables may only appear in conditions, not in COMPUTE or other mathematical expressions.
Error Number:
0429
Error Message:
"File mode could not be set to binary."
Description:
An error occurred while attempting to redirect standard output using DISPLAYFILE on a Windows®-platform computer. Reboot your computer and try again.