GDSX Manual

Operations and Support

Extended General Device Support (GDSX) Manual–134303

3-19

Abend Messages

The configured control block pool sizes may be displayed by issuing the following SCF

command:

-> INFO PROCESS $GDSX-process-name, DETAIL

Error message 10013 is sent to the home terminal when TSCODE determines that the

GDSX process is running at a high PIN. At this point TSCODE has not checked the

setting of d^plus^enabled of the CONTROLFLAGS configuration parameter. If this

parameter is set to 0, error message 10014 is sent to the home terminal, and the process

abends; if the parameter is set to 1, processing continues with no message to the home

terminal.

Error message 10015 is sent to the home terminal if from outside SCF a configuration

parameter is assigned a value containing a nonnumeric character.

Abend Messages

If the GDSX process ceases to function, it attempts to send an abend error message to

the home terminal where the process was created.

When TSCODE detects an internal inconsistency, 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 calls ABEND, so that if SAVEABEND is set for the

process (at bind time), a memory image file is 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.

GDSX problem reports should be accompanied by a SAVEABEND dump (if a dump

was generated) and the object code file (with SYMBOLS) running at the time of the

failure.

Following is the format of an abend error message:

number

is the abend error number

is the code space ID

address

is the value of the P register

process-name: INTERNAL ERROR #number AT %ee.address

Save file created: vol.subvol.filename

ABENDED: process-name