GDSX Manual

Operations and Support
Extended General Device Support (GDSX) Manual–134303
3-23
Trap Messages
Trap Messages
A trap can cause GDSX to generate a trap message and an abend message at the home
terminal, and a fault message at the EMS terminal.
When the operating system encounters a trap, the GDSX trap handler is called. The trap
handler in turn calls the procedure DIE. If debug^fatal^flag of the DEBUGFLAGS
configuration parameter is set, DIE calls DEBUG. Regardless of the value of
DEBUGFLAGS, the process will calls ABEND, so that if SAVEABEND is set for the
process (at bind time), a memory image file will be created for later investigation using
INSPECT. Should GDSX enter DIE, an abend error message is produced indicating the
internal error number, the code space ID, and the value of the P register.
Following is the format of a trap message:
number
is the trap number
ee
is the code space ID
address
is the value of the P register
Table 3-4 contains a summary of the trap messages issued by TSCODE.
Q^CPX/
PUSH^CP
The address passed is not in extended memory.
STOP^TASK^AND^CLEANUPX
(MAIN)
Stopped^bit is not set or stop^mode is set.
STOP^TASK^AND^CLEANUPX/
FREE^DCB
The address of the DCB that is to be freed is not in the
DCB table.
STOP^TASK^AND^CLEANUPX/
STOP^ACTIVE^IO
The active I/O on $RECEIVE is being canceled, but
the I/O is not a SIGNALTIMEOUT.
TAKEBREAK GDSX tries to take break ownership, but there is no
free entry in the LDCB bitmap.
WAKE^TASK The state of the current TCB is not 0, or event is
greater than or equal to 15.
process-name: TRAP number %ee.address
Save file created: vol.subvol.filename
ABENDED: process-name
Table 3-3. Error 220 Message Breakdown (page 3 of 3)
TSCODE Procedure/
Subprocedure Executing Description of Event Causing Error 220