GDSX (Extended General Device Support) Manual

Operations and Support
Extended General Device Support (GDSX) Manual—529931-001
3-21
Abend Messages
Errors Less Than 100
An abend error number less than 100 usually indicates that the system does not have
enough space to run a GDSX process. To recover, use a disk that has more free
space. If you determine there is no problem with disk space, check the configuration
parameter values.
Error 220
Internal control flags or states are not synchronized. GDSX abends at the location
where the problem is detected, although the problem may have happened long before
it was detected. Check the places where the flags were most recently updated and
check that all I/O buffers are in extended memory.
This error can occur at the beginning of the kernel’s dispatcher routine if location zero
in the GDSX process data stack is altered. To see whether this is the case, check the
value of data stack location zero (location G0 may be referenced by a variable name).
The value should be %52525. If it is not, check USCODE for uninitialized pointers.
A breakdown of error 220 messages is given in Table 3-3. Regardless of the reason
for getting this abend error, it is always a good idea to check that all I/O buffers are in
extended memory.
Error 230
The buffer pool has been corrupted. Check to see how previously allocated buffer
space has been used. The problem often occurs when data moved into a buffer
overflows the allocated area.
Error 231
The message pool has been corrupted. Check to see how previously allocated buffer
space has been used. The problem often occurs when data moved into a buffer
overflows the allocated area.
310 error^unexpected^case Case statement error
320 error^wrong^case Case statement error
500 error^q^cp Fault-tolerance processing problems
Table 3-2. Abend Error Messages
Abend
Number Literal for Error Number Description of Event Causing Abend