SNAX/APC Management Programming Manual

3: ZAPC-ERR-ALLOC-ERR-NO-RETRY
Error Numbers and Error Lists
111813 Tandem Computers Incorporated A–7
3: ZAPC-ERR-ALLOC-ERR-NO-RETRY
The operation failed. Do not retry until the condition is corrected.
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–NO–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
The SNAX/APC subsystem encountered an allocation error in the processing of a
CNOS-related command. The equivalent RETURN_CODE value defined in the IBM
Transaction Programmer's Reference Manual for LU 6.2 is ALLOCATION-ERROR. This
error indicates that the conversation could not be allocated due to a permanent
condition. This condition can occur if the session to be used by this conversation
cannot be activated because the session limit for the PTNR-MODE object is set to 0.
The condition can also occur if a system-definition error or session-activation protocol
error occurred before the conversation could be allocated.
Effect
The operation fails.
Recovery
The request should not be retried until the cause of the failure has been determined
and corrected. Check the EMS event log to identify and correct the problem.