GDSX Manual

Operations and Support
Extended General Device Support (GDSX) Manual–134303
3-27
If GDSX Abends
If GDSX Abends
If your GDSX application abends, perform the following before consulting a Tandem
support representative:
•
Record the full version procedure from the GDSX object file. You can determine
this by using either the VPROC utility or BIND. For example, using VPROC:
> VPROC
Enter filename:
> OGDS
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.
16 Task tried to close $RECEIVE.
17 Task called INIT^SEM passing a nonzero semaphore.
18 Task attempted to obtain an uninitialized semaphore.
19 Task attempted to release a semaphore it did not own.
20 Task passed an invalid task number to get a TCB address.