SNAX/APC Management Programming Manual

22: ZAPC-ERR-RES-FAIL-NO-RETRY
Error Numbers and Error Lists
A–26 111813 Tandem Computers Incorporated
22: ZAPC-ERR-RES-FAIL-NO-RETRY
A resource failure occurred.
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–
RES–FAIL–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
A resource failure occurred during the processing of a CNOS-related command. The
equivalent RETURN_CODE value, as defined in the IBM Transaction Programmer's
Reference Manual for LU 6.2, is RESOURCE_FAILURE_NO_RETRY. This error was
probably caused by an ABORT, STOP, ALTER, or START PTNR-MODE command.
The CNOS-related command did not execute successfully because of a failure that
caused the control operator conversation to be prematurely deallocated. For example,
the session being used for the control operator conversation may have been
deactivated because of one of the following reasons:
A session protocol error occurred.
A session outage from which the control operator component of the LU could not
recover occurred.
The conversation was deallocated because of a protocol error between the control
operator components of the LUs.
The session could not be established.