Expand Management Programming Manual

ERROR NUMBERS AND ERROR LISTS
6: ZEXP-ERR-TRACE-NOT-STARTED
6: ZEXP-ERR-TRACE-NOT-STARTED
An error occurred during the processing of a TRACE command
that traces the EXPAND manager process, so the tracing 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-ENUM.
ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.
Tokens
ZSPI-TKN-ERROR is the standard SPI error token, as described in
the
Distributed Systems Management (DSM) Programming Manual
. Its
value consists of the EXPAND subsystem ID and the error number
ZEXP-ERR-TRACE-NOT-STARTED. This token is always present in the
error list.
ZCOM-TKN-OBJNAME is an object-name token that contains the name
of the EXPAND manager process. This token is always present
in the error list, and it is described in Section 6, "Common
Definitions."
ZCOM-TKN-OBJTYPE is the object type ZCOM-OBJ-NULL. This token
is always present in the error list, and it is described in the
Communications Management Programming Manual
.
Probable Cause
An incorrect value was given in the extensible structured token
ZCOM-MAP-TRACE-MODIF. The trace is not started.
Recommended Action
Correct the value or values that caused the error.
A-12