Perform component tracing on the systems in the sysplex

The operator performs the tasks. Note that these tasks are for a specific component trace, rather than for a trace started by the system at initialization.

1. Start the component traces: On a console with MVS™ master authority on one system in the sysplex, the operator enters a ROUTE command containing a TRACE CT command. (The ROUTE command can be used only on MVS systems with JES2.)

The command specifies a parmlib member with the same name in each system being traced. Note that, if parmlib members are not specified, all systems issue message ITT006A to prompt for options. If the component to be traced does not have a parmlib member, specify the IBM-supplied CTIITT00 member to avoid the prompts.

Example 1: Command to start traces in all systems: The command starts the trace in all systems in the sysplex.

route *all,trace ct,on,comp=sysxcf,parm=ctwxcf33

Example 2: Command to start traces in some systems: The command starts the trace in a subset of systems. Both commands specify the CTWXCF33 parmlib member on each system being traced.

route subs2,trace ct,on,comp=sysxcf,parm=ctwxcf33

Example 3: Command for a component without a parmlib member: The following command turns on tracing for a SYSVLF trace in the systems of a sysplex, without prompts for replies to the TRACE command. The SYSVLF component trace has no parmlib member.

route *all,trace ct,on,comp=sysvlf,parm=ctiitt00

2. Verify that the traces Are running: See Verifying component tracing.

3. Obtain the dumps containing the component trace records: The operator requests an SVC dump for each system being traced.

Example: DUMP command for systems in a sysplex: The example shows the DUMP operator command entered on a console with MVS master authority on one system in the sysplex. The reply requests dumps on all of the systems named in the pattern of S*. The example assumes that the systems being traced have the following names: S1, S2, S3, and S4; any other systems in the sysplex have names that do not fit the pattern, such as B1 or T2.

dump  comm=(dump for xcf component trace)
* 32 IEE094D ...
r 32,remote=(syslist=(s*)),end
 .
 .
 .
IEA911E ...

The system identifies the data set containing the dump in message IEA911E. If an exit moves a dump, the operator should look for a message identifying the data set containing the moved dump and tell you the name of the dump and the data set containing it.

4. Stop the component traces: On a console with MVS master authority on one system in the sysplex, the operator enters a ROUTE command containing a TRACE CT,OFF command to stop the traces. (The ROUTE command can be used only on MVS systems with JES2.)

Example 1: Command to stop traces in all systems: The command stops the traces in all systems in the sysplex.

route *all,trace ct,off,comp=sysxcf

Example 2: Command to Stop Traces in Some Systems: The command stops the traces in a subset of systems in the sysplex.

route subs2,trace ct,off,comp=sysxcf