SNAX/APC Management Programming Manual

36: ZAPC-ERR-UPPER-OBJ-NOT-STARTED
Error Numbers and Error Lists
111813 Tandem Computers Incorporated A–41
36: ZAPC-ERR-UPPER-OBJ-NOT-STARTED
The parent object was not started.
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–
UPPER–OBJ–NOT–STARTED 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
Either an ADD SESSION command was rejected because its parent PTNR-MODE
object is not in the STARTED state, or a START command was rejected because the
target object’s parent was not currently in the STARTED state.
Effect
The ADD or START command fails.
Recovery
Activate the parent object before attempting to add a session or start a subordinate
object.