z/VM: CP Commands and Utilities Reference - z/VM - IBM

TRSOURCE
Authorization
Purpose
Usage Notes
Privilege Class: C
Use the TRSOURCE command to support definitions and control of I/O, data, and
guest tracing.
The TRSOURCE command is functionally organized as follows:
v TRSOURCE ID defines a trace. TRSOURCE ID associates an event (such as
execution of a particular piece of code or an interrupt on a specific device) with a
name (traceid) and, optionally, with a set of other traces (traceset).
The TYPE operand of TRSOURCE ID assigns a trace ID to one of the three
trace types. These types are:
1. IO (I/O tracing). The IO trace lets you trace all I/O activity for a specific real
device or range of real devices. The times, channel programs, SCSWs and
data transferred for each I/O operation to the specified devices are made
available for data analysis.
2. DATA (data tracing). The data trace allows the user to define trace entries
dynamically to record execution of most code paths in CP. The LOC
parameter specifies what instruction, when executed, triggers recording of
information. Data link parameters define what information is collected when
the trap starts.
3. GT (guest tracing). The guest trace allows CMS or GCS to record events in a
system trace file.
v TRSOURCE ENABLE activates the tracing of individual trace IDs and of trace
IDs within trace sets.
v TRSOURCE DISABLE deactivates the tracing of individual trace IDs and of trace
IDs within trace sets.
v TRSOURCE DROP disables and drops all CP knowledge of individual trace IDs
and trace IDs within trace sets.
v TRSOURCE DISPLAY displays the status resulting from the TRSOURCE
commands you have issued.
See z/VM: Diagnosis Guide for examples that show how TRSOURCE is used.
(General for TRSOURCE)
1. All traces are disabled at system termination.
TRSOURCE
2. The definitions of traces are not saved across system IPLs. Therefore, the
definitions of any commonly defined traces should be saved in EXECs.
3. When a new member of an enabled set is defined, that member is not
automatically enabled. It must be enabled separately. Attempts to enable trace
IDs that are already enabled do not alter anything and do not result in an error
message.
4. The definition of what is being traced for each trace ID cannot be altered while
the trace ID is enabled. Any trace ID may be altered while it is disabled.
Chapter 2. CP Commands 1673