GDSX (Extended General Device Support) Manual

Operations and Support
Extended General Device Support (GDSX) Manual529931-001
3-19
Abend Messages
10010 maxPCBpool or previous pools too large
10011 Sum of all max***pools are > 16777216d
10012 Sum of final EXT. MEM size > 16777216d
10013 GDSX process to run converted at high PIN - continuing
10014 GDSX process running high PIN not enabled - terminating
10015 Nonnumeric char in configuration param
10016 Number of tasks exceed limit with TMF
10017 Task size is too small (Param TASKSIZE)
For example, if the TCB and IOCB pool sizes have been calculated, and the total
requirement for the TCB and IOCB pools, the extended buffer pool, and the extended
message pool exceeds 16,777,216 bytes, the following error message is sent to the
home terminal:
10003 maxIOCBpool or previous pools too large
If the total calculated for all the control block pools, the extended buffer pool, the
extended message pool, and the checkpoint buffer exceeds 16,777,216 bytes, error
message 10011 is sent to the home terminal. If the total calculated for all the areas to
be allocated in the extended segment exceeds 16,777,216 bytes, error message
10012 is sent to the home terminal.
Error message 10001 is sent to the home terminal if a configuration parameter other
than a control block pool size configuration parameter (see the above external
parameter names) is assigned a value greater than 65,532.
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.