Explanation
A error was detected in one
of the internal data structures. The reason code contained in Register
15 indicates the exact nature of the error.
- Reason
- Explanation
- 1
- The free pool of connection table entries was exhausted; sufficient
entries should have been allocated during initialization.
- 2
- An incorrect connection entry address was found in the word immediately
preceding the RPL record passed to an allocate request.
- 3
- An incorrect connection entry address was found in the word immediately
preceding the RPL record passed to a deallocate request.
- 4
- An incorrect connection entry address was found in the word immediately
preceding the RPL record passed to a send request.
- 5
- An incorrect connection entry address was found in the word immediately
preceding the RPL record passed to a receive request.
- 6
- The RPL address returned from a VTAM® deallocate
request does not match either the send or receive RPL address.
- 7
- The VTAM send queue was
empty when it was expected to contain an entry.
- 8
- A counter, which contains the number of entries in the VTAM send, contains a negative
number.
- 9
- An attempt to terminate a connection with a destination node has
failed because of a probable program logic error.
- 10
- An error occurred while adding a connection to the time-out inactivity
list; the connection entry address did not reference a valid connection
table entry.
- 11
- A connection table entry has been lost from the time-out inactivity
list.
- 12
- The RPL address returned from VTAM for
a conversation allocation request did not match either the send or
receive RPL address.
- 13
- The free pool for the pending message queue was exhausted; sufficient
entries should have been allocated during initialization.
System programmer response
Contact the IBM® Software Support Center.