
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
batch mode,
the program will terminate immediately.
- 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
- UNUSED
- UNUSED
- 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 or batch 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 command 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 encountered.
ACTION: Check input line for extra characters. Any
characters behind ';' are ignored.
- *** EXPRESSION NOT DEFINED
- An attempt was made to interpret the command 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 command file.
ACTION: the
quoted was probably used in a statement 'DO LB_ ...' or
in a conditional GOTO statement, and the destination
label was omitted.
ACTION: Insert the label
at the appropriate place.
- *** NO "EN" COMMAND ENCOUNTERED. TERMINATION ASSUMED
- The batch file is not terminated with
'EN' or
'RE'.
ACTION: Next time you run the
batch file, make sure it is properly terminated.
- *** 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 '.'.
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 6 arguments are used in the calling batch or
procedure command file.
ACTION: Reduce number of
arguments to 6 or less.
- *** TOO MANY RETURNS SPECIFIED
- Inconsistencies in the bookkeeping of the procedure
nesting level.
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
operation.
- *** 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 operation,
procedure, or arithmetic expression.
ACTION: Check
command string for syntax errors.
- *** UNKNOWN MODE
-
The MODE command (' MD') was
used with an undefined option.
ACTION: check list of
options available by using the Mode '
ME' (MODE Menu command)
- *** 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 expression.
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 and pseudo-batch runs controlled by
SPIDER command files, it is important to know the mechanism of the
procedure call.
Entering a SPIDER command with the general format @filename
(where filename is eight 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 brocedure.
Similarly, entering a command with the general format filename (where
filename consists of the character 'B' for 'batch' and two digits; e.g. B09) will cause the
system to look for a file named filename.projectcode
In both cases, a 'working copy' of the file is first produced with the
name filenameX.projectcode respectively.
In the case of the pseudo-batch command file, the working copy is
identical with the source file.
In the case of a procedure command file, the working copy is an
execution-time translation of the source file. Subject to substitution
are all unresolved input parameter expressions. Take the example of a
source file called shift5.sys which has the form:
-
- ; SHIFT5.SYS - SHIFT IMAGE BY (5,5)
- SH
- ?INPUT FILE?
- ?OUTPUT FILE?
- (5,5)
- RE
-
In this case, a calling (pseudo-batch, interactive, or procedure)
sequence:
- @SHIFT5
- PIC001
- OUT001
-
will cause the file shift5.sys to be translated into a working copy,
stored in SHIFT5X., which has the form
- SH
- PIC001
- OUT001
- (5,5)
- RE
If a pseudo-batch or procedure run stops unexpectedly, you should
first check the RESULTS. file to see where exactly the error
occurred and check whether an error message is printed.
If this check is inconclusive, and the command file has no obvious
syntactical errors, it may be helpful to check the current working
copy using the editor. This will tell you whether or not the
run-time substitutions made by the system correspond to the expected
sequence of processing.
Check the User's guide for a
more complete description of the SPIDER command syntax.
Source: errors.html
Last update: Dec. 09 1997
ArDean Leith
©
Copyright Notice /
Enquiries: spider@wadsworth.org