Publication 1747-RM001G-EN-P - November 2008
16-8 Troubleshooting Faults
0025 Excessive stack depth/JSR calls for
the STI routine.
A JSR instruction is calling for a file
number assigned to an STI routine.
Correct the user program to meet the
requirements and restrictions for the
JSR instruction, then reload the
program and run.
0026 Excessive stack depth/JSR calls for
an I/O interrupt routine.
A JSR instruction is calling for a file
number assigned to an I/O interrupt
routine.
Correct the user program to meet the
requirements and restrictions for the
JSR instruction, then reload the
program and run.
0027 Excessive stack depth/JSR calls for
the user fault routine.
A JSR instruction is calling for a file
number assigned to the user fault
routine.
Correct the user program to meet the
requirements and restrictions for the
JSR instruction, then reload the
program and run.
0028 Invalid or non-existent “startup
protection” fault routine file value.
• Either a fault routine file
number was created in the
status file, but the fault
routine file was not physically
created, or
• the file number created was
0, 1, or 2.
• Either disable the fault routine
file number (S:29) in the
status file, or
• create a fault routine for the
file number referenced in the
status file (S:29). The file
number must not be 0, 1, or 2.
0029 Indexed address reference is outside
of the entire data file space (range of
B3:0 through the last file).
The program is referencing through
indexed addressing an element
beyond the allowed range. The range
is from B3:0 to the last element of the
last data file created by the user.
Correct and reload the user program.
This problem cannot be corrected by
writing to the index register word
(S:24).
002A Indexed address reference is beyond
the specific referenced data file.
The program is referencing through
indexed addressing an element
beyond a file boundary.
Correct the user program, allocate
more data space using the memory
map, or re-save the program allowing
crossing of file boundaries. Reload
the user program. This problem
cannot be corrected by writing to the
index register word (S:24).
002B An invalid file number for an indirect
address exists.
The file number exists, but it is not
the correct file type or the file number
does not exist.
Check the file type or create the file
number.
002C The referenced indirect address
element is outside data file limits.
The indirectly referenced element
does not exist, but the file type is
correct and it exists.
Create the indirectly referenced
element.
Table 16.3 Run Errors (Continued)
Error Code
(Hex)
Description Probable Cause Recommended Action
ATTENTION
The SLC processor uses an index value of zero for the faulted instruction following error
recovery.
To Next Page
Loading...
Need help?
General
