The values for the OPTIONS parameter for the CTnOPSxx parmlib member
and reply for a TRACE command, in alphabetical order, are:
- COMMAND
- Traces events related to command processing.
- CONSDATA
- Traces events related to console state changes.
- LOGGING
- Traces events related to Operlog and Syslog processing.
- MCACHE
- Traces events related to the message cache.
- MESSAGES
- This option includes the WTO, MSGDLVRY, MCACHE and LOGGING options.
- MSG=msgid
- Traces processing of a specific message. It REQUIRES either one
of the following OPTIONS: MESSAGES, WTO, MSGDLVRY, MCACHE or LOGGING. msgid is
1-10 alphanumeric characters in length indicating the message id that
will be traced.
- MSGDLVRY
- Traces events for WQE processing, MCS console message queueing,
and extended MCS console message processing.
- RECOVERY
- Traces recovery events.
- SERIALIZ
- Traces latch serialization events.
- SYSPLEX
- Traces events for XCF signalling, sysplex serialization services,
sysplex clean-up processing, and the manipulation of various queues.
- WTO
- Traces the effects of MPFLSTxx, the user exits, and the SSI on
message content and attributes.
These additional options increase the number of trace records the
system collects and can slow system performance. Each time you change
the trace options, you must respecify any options you want to keep
in effect from the last trace.
Note: Before you use the MESSAGES, WTO, MSGDLVRY, MCACHE or LOGGING
options, you should do the following:
- Increase the buffer size
- Start and connect the external writer.
This is especially important if you are starting tracing at IPL
This might not be necessary if you are tracing a message ID since
you would only be cutting records for the particular message.