GDSX (Extended General Device Support) Manual

Operations and Support

Extended General Device Support (GDSX) Manual—529931-001

3-24

EMS Event Messages

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

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.

EMS Event Messages

These status, warning, and error messages are always directed to the $0 collector. All

EMS event messages have the following format:

process-name: TRAP number %ee.address

Save file created: vol.subvol.filename

ABENDED: process-name

Table 3-4. TSCODE Trap Messages

Fault Number Description of Cause

0 Illegal address trap

1 Instruction failure trap

2 Arithmetic overflow trap

3 Stack overflow trap

4 Looptimer trap

11 No memory (Guardian) trap

12 Uncorrectable memory error trap

13 Map parity error trap

hh:mi:ss: mm/dd/yy name (cpu,pin) message-type - text