OSI/TS Management Programming Manual

TRACE PROCESS Command
Commands and Responses
056786 Tandem Computers Incorporated 5–203
The default value of ZREC-SIZE may not be large enough to allow complete
formatting of trace records using PTrace. Formatting of DSM commands and
responses (using the formatted or LABEL facility in PTrace) requires a large
ZREC-SIZE to accommodate the entire SPI buffer. If you are using this feature,
you should specify a ZREC-SIZE of between 1000 and 4000 bytes.
ZCOM-TKN-CMD-TIMEOUT
is described in the Communications Management Programming Manual. This token is
optional; duplicate occurrences are not allowed.
ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKN-
COMMENT
are described in the Distributed Systems Management (DSM) Programming Manual.
These tokens are optional and, with the exception of ZSPI-TKN-COMMENT,
duplicate occurrences are not allowed.
Tokens in Response Buffer
ZSPI-TKN-DATALIST and the final ZSPI-TKN-ENDLIST
enclose a data list, as described in the Distributed Systems Management (DSM)
Programming Manual. These tokens enclose the other response tokens only if the
value of the header token ZSPI-TKN-MAXRESP is nonzero. No more than one
data list can appear in the response.
ZCOM-TKN-OBJTYPE
specifies the type of object named in ZCOM-TKN-OBJNAME. The token value is
ZCOM-OBJ-PROCESS.
ZCOM-TKN-OBJNAME
is the name of the process that was to be traced.
ZSPI-TKN-RETCODE
indicates whether or not the command was successful. If the command failed, this
token supplies the reason for the failure. Its use is described further in the
Distributed Systems Management (DSM) Programming Manual.
ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST
enclose a standard SPI error list, as described in the Distributed Systems
Management (DSM) Programming Manual.
Operational Note
This command can be used to start a trace, stop a trace, or change the current
attributes of a trace operation. For further information about tracing, refer to the
Subsystem Control Point (SCP) Management Programming Manual.