Trace Control Statements
The control statements control the trace facility in all environments.
Control Statements
The control statements are input to the Trace Facility, so it knows where to send trace output for each type and level of message. The following table describes each of the control statements.
Control Statements
Control | Parameter List | Description |
|---|---|---|
WZZLOGA= | DESTINATION | Destination A for Log messages. |
WZZLOGB= | DESTINATION | Destination B for Log messages. |
WZZDBGA= | DESTINATION | Destination A for Trace messages. |
WZZDBGB= | DESTINATION | Destination B for Trace messages. |
ERRORM= | DESTCODE,DESTCODE,etc. | Destinations for Error level messages. |
WARNM= | DESTCODE,DESTCODE,etc. | Destinations for Warning level messages. |
INFOM= | DESTCODE,DESTCODE,etc. | Destinations for Information level messages. |
DEBUGM= | DESTCODE,DESTCODE,etc. | Destinations for Debug level messages. |
TRACEM= | DESTCODE,DESTCODE,etc. | Destinations for Trace level messages. |
DEBUG= | CMPNTCODE,CMPNTCODE,etc. | List of components to enable for Debug level messages. |
TRACE= | CMPNTCODE,CMPNTCODE,etc. | List of components to enable for Trace level messages. |
Trace Destination Codes
The trace destination codes describe the destinations to which the messages should be written. Multiple destinations can be specified, separated by commas.
Valid Values
- DSA – WZZLOGA or WZZDBGA, depending on the type of message.
- DSB – WZZLOGB or WZZDBGB, depending on the type of message.
- TPUT – issues the message as TPUT. This only works under TSO.
- WTO – issues the message via WTO to ROUTCDE=(11), MCSFLAG=(HRDCPY).
Trace Destinations
Two destinations can be defined for each type of message. That is, destinations A and B can be defined for both log and trace messages.
Valid Values
- Fully qualified dataset name – the dataset is dynamically allocated and used. If the allocation fails, an error message will be issued, and the destination becomes mute.
- SYSOUT=x – a sysout dataset of class x will be allocated and used. If the allocation fails, an error message will be issued, and the destination becomes mute.
- DD:ddname – will use the indicated DDNAME. It is assumed that the DDNAME has been allocated in the startup JCL, TSO allocate commands, or wherever is appropriate. If the DDNAME fails open, an error message will be issued, and the destination becomes mute.
- * – a dynamic allocation of TERM=TS is attempted. This is the same as “ALLOC F(xxx) DA(*)” on TSO. If the allocation fails, an error message will be issued, and the destination becomes mute.
- Blank – a blank operand will set this destination to mute state.
What is a Mute Trace Destination?
When a trace destination is in the mute state, no trace or log output is generated to that destination. This situation does not cause a performance problem or reflect any kind of error to the rest of the Code Pipeline processing.
Component List
The component list should be set to NONE on the DEBUG and TRACE control statements. The Support staff will advise the values to place here for problem diagnosis.