GDSX (Extended General Device Support) Manual

Operations and Support
Extended General Device Support (GDSX) Manual—529931-001
3-27
Fault Messages
hh is hour
mi is minute
ss is second
mm is month
dd is day
yy is year
name is process name
Fault messages generated by converted GDSX processes always show the PIN with a
value of 255.
Here is an example of a fault message:
09:23:00 04/10/91 $GDSX (06,37) error - TERM 01
($GDSX.#T27B)
Fault # 104 P =
%00.047502
Table 3-7 contains a summary of the fault messages issued by TSCODE. Fault
numbers 0-4 and 10-13 are usually generated by the GDSX trap handler.
Table 3-7. TSCODE Fault Messages
Fault Number Description
0 Illegal address trap.
1 Instruction failure trap.
2 Arithmetic overflow trap.
3 Stack overflow trap.
4 Looptimer trap.
5 Message fault. GDSX was unable to obtain word-addressable memory
to queue a message for the task.
6 Reply fault. Task made an incorrect call to ^REPLY. Reply error was
either 60, or more than 200 and less than or equal to 254.
7 Sendmsg fault. Error occurred when issuing a message.
8 Context fault. Task gave up control when the size of its working stack
exceeded the size specified by TASKSIZE.
9 Incorrect parameter used to allocate or deallocate pool space.
10 Memory manager (Guardian) trap.
11 No memory (Guardian) trap.
12 Uncorrectable memory error trap.
13 Map parity error trap.
14 IOCB fault. GDSX was unable to allocate an IOCB to handle an I/O
request.
15 Checkpoint fault. Incorrect parameter to call CHECKPOINT routines, or
task has too much buffer space to checkpoint.