SPIDER ERROR MESSAGES AND DEBUGGING
Contents of this Document
SPIDER error messages may be due to:
- An operation error during a specific operation. An operation error message will be printed. If
SPIDER is being run interactively the user may continue
with another operation. However if SPIDER is in procedure mode, the program will
- A system error during the language pre-processing phase, caused
typically due to incorrect syntax being detected by the command
interpreter. A system error message
will be printed. Below is a brief explanation as to why such an
error may have occured. Such errors are always fatal!
Each Error Message has an associated Error Number from 1
to 38, except for the error message ``.SEE EXPLICIT STATEMENT''
which has an Error Number of 100. The Error Numbers and the
corresponding Error Messages are:
- INCONSISTENT PICTURE DIMENSIONS
- OPERATION NOT CONSISTENT WITH DATA FORMAT
- ROWLENGTH TOO LARGE FOR BUFFER
- OPENING FILE
- NORMALIZING DATA
- INSUFFICIENT BUFFER SPACE
- I/O RECORD NUMBER OUT OF LIMITS
- DIMENSIONS NOT POWER OF TWO
- PICTURE DIMENSIONS EXCEED FRAME
- READING FILE
- INITIALIZING TAPE
- INCONSISTENT INPUT PARAMETERS
- FILE IS WRITE PROTECTED
- BAD INPUT PARAMETER(S) .RE-ENTER:
- END-OF-FILE ON INPUT
- FILE DOES NOT EXIST
- TOO MANY FILE NUMBERS ENTERED
- NOT DEFINED...
- DATA FILE PARAMETER ERROR
- TOO MANY PROCEDURES
- UNKNOWN OPTION
- SLICE NUMBER OUT OF BOUNDS
- NOT CONTAINED IN TABLE
- UNDEFINED ERROR
- UNABLE TO CONSTRUCT FILE NAME
- NUMBER OF PROJECTIONS TOO LARGE
- POOR PHASES
- TMPARY FULL, SHORTEN YOUR FILENAMES?
- PARAMETER VALUE OUT OF LEGAL RANGE
- PROGRAM TRAP
- ACCURACY NOT ACHIEVED
- OVERFLOW PROTECTION
- FILE EXISTANCE ERROR
- ILLEGAL ARGUMENT RANGE
- ONLY FIXED IMAGE SIZE ALLOWED
- IMAGE SIZE IS PRODUCT OF PRIMES
- *** ARITHMETIC ASSIGNMENT FAILED
- In a pocketcalc arithmetic
assignment, a syntax error was found.
ACTION: Check syntax
- *** ARGUMENT MISMATCH IN PROCEDURE
- The number of arguments used in the calling procedure command sequence does not
agree with the number of arguments in the procedure called.
ACTION: Make sure the argument lists have the same length.
- *** END-OF-FILE DURING READ IN SEARCH
- After incrementing a DO-loop
index, the DO operation was no longer
found in temporary file.
ACTION: error unlikely. Notify Albany.
- *** ERROR IN REGISTER SUBSTITUTION
- A query was answered with a register, but a syntax error was
ACTION: Check input line for extra characters. Any characters
behind ';' are ignored.
- *** EXPRESSION NOT DEFINED
- An attempt was made to interpret the operation line as an
arithmetic expression, but the expression is not defined.
ACTION: check expression for syntax errors.
- *** FATAL ERROR ENCOUNTERED IN BATCH MODE
- An unrecoverable error has been encountered, and the global
error flag requested immediate termination.
ACTION: See specific error message for more information.
- *** LABEL NOT FOUND: XXX
- The label printed in the error statement at the place marked
'XXX' could not be found in the procedure file.
ACTION: the quoted was probably used in a statement 'DO LB_ ...' or
in a conditional GOTO statement, and the destination label was
ACTION: Insert the label at the appropriate place.
- *** NO "EN" COMMAND ENCOUNTERED. TERMINATION ASSUMED
- The procedure file is not terminated with 'EN' or 'RE'.
ACTION: Next time you run the procedure file, make sure it is properly
- *** OPERATION NOT ALLOWED IN BATCH MODE
- *** OPERATION NOT ALLOWED IN INTERACTIVE MODE
- *** PROCEDURE FILE CANNOT CALL BATCH FILE
- *** PROCEDURE FILE DOES NOT EXIST XXX
- The procedure file named XXX could not be found under
extensions '.SYS' or '.<PRJ>'.
ACTION: make sure the file exists with either extension.
- *** PROCEDURE NESTING LEVEL (12) EXCEEDED
- *** SPIDER STOP -- UNABLE TO CONSTRUCT LOG FILE
- An error was made in the specification of the project code, and
the name of an auxiliary file could not be constructed.
ACTION: Make sure project code has three valid characters and you
have write permissions in the local directory.
- *** TOO MANY ARGUMENTS IN PROCEDURE
- More than 12 arguments are used in the calling procedure or
procedure command file.
ACTION: Reduce number of arguments to 12 or less.
- *** TOO MANY RETURNS SPECIFIED
- Inconsistencies in the bookkeeping of the procedure nesting
ACTION: Error unlikely. Notify Albany.
- *** UNDEFINED EXPONENTIATION
- A non-integer exponent was used on a negative number, or on the
negative-valued result of an arithmetic expression.
ACTION: Check expression for consistency with intended
- *** UNEXPECTED ERROR DURING PROCEDURE RUN
- A serious error condition was encountered during the procedure run.
ACTION: Check procedure file for syntax errors.
- *** UNIDENTIFIED COMMAND STRING
- The command string could not be interpreted as an operation,
procedure, or arithmetic expression.
ACTION: Check string for syntax errors.
- *** UNKNOWN MODE
- The MODE operation (' MD') was used
with an undefined option.
ACTION: check list of options available by using the Mode ' ME' (MODE Menu operation)
- *** UNRESOLVED SYMBOLIC REFERENCE
- A symbolic parameter was used in the procedure, whose reference input
line could not be found.
ACTION: Re-count the symbolic parameters to make sure that they
refer to existing input lines.
- *** ZERO DIVISION
- An attempt was made to divide by zero in an arithmetic
ACTION: Make sure the value range of a register variable will not
allow zero division to occur. Use logical- IF bypass if necessary.
For the debugging of procedure runs controlled by SPIDER procedure
files, it is important to know the mechanism of the procedure call.
Entering a SPIDER operation with the general format
@filename (where filename is 40 or fewer alphanumeric
characters; e.g. @ROTAV) will cause the system to look for a file
named filename.projectcode where projectcode is the project
code that is set upon starting SPIDER or set with the NC operation. If this file does not exist -- the
file filename.sys residing in the directory defined by the
system environmental variable SPPROC_DIR in the login file is used
for the procedure.
In the case of a procedure file, symbolic parameter references
contained in the file translated at execution-time. Subject to
substitution are all unresolved input parameter expressions. Take
the example of a source file called shift5.sys which has the
If a procedure run stops unexpectedly, you should check the
RESULTS. file to see where exactly the error occurred and check
whether an error message is printed. Since file output is buffered,
the RESULTS file may not contain the actual final output.
The MY FL operation will flush any
pending ouput to the RESULTS file.
- ; SHIFT5.SYS - SHIFT IMAGE BY (5,5)
- ?INPUT FILE? <1>
- ?OUTPUT FILE? <2>
- In this case, a calling (interactive, or procedure)
- will cause the file shift5.sys to be translated into the
Check the User's guide for a more
complete description of the SPIDER command syntax.
Source: errors.html Last update: Jan.
30 2001 ArDean Leith
Copyright Notice /