The component trace service provides a way for MVS™ components to collect problem data about
events. Each component that uses the component trace service has
set up its trace in a way that provides the unique data needed for
the component. A component trace provides data about events that occur
in the component. The trace data is used by the IBM® Support Center, which uses the trace data
to:
- Diagnose problems in the component
- See how the component is running.
Usage of System Resources: Some component traces use minimal system resources, especially while tracing a small number of events. These minimal traces often run anytime the component is running. Other traces use significant system resources, especially when many kinds of events are traced. These large traces are usually requested only when the IBM Support Center asks for them.
Run concurrent traces: You can run more than one
component trace at a time; you can run component traces:
- Concurrently for several components on one system.
- Concurrently for one or more components on some or all of the systems in a sysplex.
- Concurrently for one component on a system. Multiple concurrent traces for a component are sublevel traces.
- Concurrently for several components on some or all of the systems in a sysplex and with sublevel traces.
The following topics describe tasks for component traces:
- Planning for component tracing tells you about the tasks needed to plan component tracing.
- Obtaining a component trace tells you how to request a specific component trace that is needed to diagnose a problem. The tasks depend on where you plan to put trace output and if you are running traces on multiple systems in a sysplex; therefore, requesting traces is presented in three topics:
- Verifying component tracing tells how an operator can check that a requested trace is running and that a component trace writer is running.
- Viewing the component trace data tells you how to format the trace output.
This topic uses tables to show the similarities and differences in the individual traces from different components. Table 1 summarizes each BCP component trace that uses the component trace service.
| Component | Reference |
|---|---|
| Advanced Program-to-Program Communication/MVS (APPC/MVS) | SYSAPPC component trace |
| Base control program internal interface (BCPii) | SYSBCPII component trace |
 Basic HyperSwap® socket support |
SYSBHI component trace |
| Common Event Adapter (CEA) | SYSCEA component trace |
| Cross-system coupling facility (XCF) | SYSXCF component trace |
| Cross-system extended services (XES) | SYSXES component trace |
| Data lookaside facility (DLF) of VLF | SYSDLF component trace |
| Distributed function of SOMobjects® | SYSDSOM component trace |
| Global resource serialization | SYSGRS component trace |
| Allocation Component | SYSIEFAL component trace |
| IOS Component Trace | SYSIOS component trace |
| JES common coupling services | SYSJES component trace |
| JES2 rolling trace table | SYSjes2 component trace |
| Library lookaside (LLA) of contents supervision | SYSLLA component trace |
| z/OS® UNIX System Services (z/OS UNIX) | SYSOMVS component trace |
| Operations services (OPS) | Requesting a SYSOPS trace |
| Resource recovery services (RRS) | SYSRRS component trace |
| Real storage manager (RSM) | SYSRSM component trace |
| Service processor interface (SPI) | SYSSPI component trace |
| System logger | SYSLOGR component trace |
| System REXX | SYSAXR component trace |
| Transaction trace (TTRC) | SYSTTRC transaction trace |
| Virtual lookaside facility (VLF) | SYSVLF component trace |
| Workload manager (WLM) | SYSWLM component trace |
A program product or application, if authorized, can also use the
component trace service to provide an application trace.
See the documentation for the program product or application for information
about its trace.
- See &ieae200t; for the CTncccxx parmlib member.
- See &ieag100t; for the TRACE CT command.
- See &ieac500t; for the COPYDUMP, COPYTRC, CTRACE, GTFTRACE, and MERGE subcommands.
- For a description of these messages, use LookAt or see MVS System Messages.
- See &ieaa800t; for information on creating an application trace.