SNAX/APC Management Programming Manual

4: ZAPC-ERR-ALLOC-ERR-RETRY
Error Numbers and Error Lists
A–8 111813 Tandem Computers Incorporated
4: ZAPC-ERR-ALLOC-ERR-RETRY
The operation failed: retry the operation.
ZSPI–TKN–ERRLIST token–type ZSPI–TYP–LIST.
ZSPI–TKN–ERROR token–type ZSPI–TYP–ERROR.
ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING
ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-STRING
ZSPI–TKN–ENDLIST token–type ZSPI–TYP–SSCTL.
ZSPI–TKN–ERROR
is the standard SPI error token, as described in the SPI Programming Manual. Its
value consists of the subsystem ID and the error number found in the ZAPC–ERR–
ALLOC–ERR–RETRY token. ZSPI–TKN–ERROR is always present in the error
list.
ZCOM-TKN-OBJNAME
is the first object name provided with the command on which the error occurred.
This token is always present in the error list, and is described in Section 4,
“Common Definitions.”
ZCOM-TKN-OBJTYPE
is the object type provided with the command on which the error occurred. This
token is always present in the error list, and is described in Section 4, “Common
Definitions.”
Cause
This error is similar to ZAPC-ERR-ALLOC-ERR-NO-RETRY; however, the condition
that caused this error may be temporary. The error condition indicates that the
START, STOP, ABORT, or ALTER operation on the PTNR-MODE object failed due to
the failure to allocate a CNOS conversation with the partner LU.
The error is equivalent to the error code ALLOCATION ERROR, as defined in the IBM
Transaction Programmer's Reference Manual for LU 6.2. This condition may be caused by
a temporary lack of resources at the local LU or the partner LU. It can also occur if the
session was deactivated by a session outage before the conversation could be
allocated.
Effect
The START, STOP, ABORT, or ALTER operation on the PTNR-MODE object failed.
Recovery
Retry the request.