SNAX/APC Management Programming Manual

32: ZAPC-ERR-TRACE-NOT-STOPPED
Error Numbers and Error Lists
111813 Tandem Computers Incorporated A–37
32: ZAPC-ERR-TRACE-NOT-STOPPED
Tracing was not stopped.
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–
TRACE–NOT–STOPPED 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 DELETE LU command is rejected because the LU trace is still in the ACTIVE state.
The trace can be stopped by the TRACE STOP command.
Effect
The DELETE LU command fails.
Recovery
Issue the TRACE LU, STOP command, then issue the DELETE LU command.