System Messages - Alphabetical List *Illegal .PROGRAM statement* (-467) Explanation: An attempt has been made to: (1) enter a line other than a .PROGRAM statement as the first line of a program, or (2) enter a .PROGRAM statement that contains a syntax error. User action: Move below the first line of the program, or reenter the line correctly. (With the eV+ SEE editor, you can press the Undo function key or press Esc+Ctrl+C to cancel the changes you have made to a .PROGRAM line.) *Illegal record length* (-528) Explanation: An FOPEN instruction has specified a record length that is not acceptable.
For example, the value is negative or too large, or the record length is zero with random-access mode specified. User action: Edit the program to specify a correct record length or specify sequential-access mode. *Illegal use of belt variable* (-466) Explanation: A belt variable has been used in a context where it is not allowed, probably in a compound transformation but not at the left-most position. User action: Edit the program to use the belt variable correctly. *Illegal user LUN specified* (-527) Explanation: An I/O instruction has specified a logical unit number (LUN) that is not defined in the eV+ system, or cannot be accessed in the manner attempted.
(See the description of the ATTACH instruction for a list of the valid logical unit numbers and the devices to which they apply.) User action: Edit the program to use a logical unit number appropriate for the instruction. *Illegal value* (-402) Explanation: A numeric or expression value that is not in the allowed range was specified within a command or instruction. User action: Edit the program to use a legal value. *Illegal when command program active* (-419) Explanation: A command program is active and an attempt has been made to execute a command that interferes with operation of the command program.
(For example, processing a ZERO command causes the command program to be deleted from the system memory.) User action: Edit the command program and delete the command causing the error. eV+Language Reference Guide, v2.x, 18319-000 Rev A Page 616