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

TRSOURCE
Examples
5. Use of the DROP keyword directed toward a trace set removes any record of
all the trace IDs in the set. To remove or ungroup a member of a set, either
assign the trace ID to another, possibly unused, trace set name or assign the
trace ID to a trace set name of NULL.
6. The destination of trace data can be altered with the TRSAVE command while
the trace is disabled. See “TRSAVE” on page 1665 for details.
7. Enabling a trace for which TRSAVE has not been issued invokes the TRSAVE
destination defaults.
8. If an error message is generated for a trace definition, enter query trsource
id traceid to verify that the trace definition is correct.
9. Data traced from this command is stored as a system data file (SDF),
specifically a trace file (TRF), as opposed to a printer or reader file. Use the
TRACERED utility to merge and format the files. TRACERED can send the
output to your virtual printer, to a CMS file, or to an OS QSAM file. For more
information, see “TRACERED” on page 1873.
10. If an external security manager is installed on your system, you may not be
authorized to issue this command. For additional information, contact your
security administrator.
The following examples provide an overview of the ways TRSOURCE can be used.
For further examples, see z/VM: Diagnosis Guide.
1. This example defines and enables a trace ID of type DATA. The trace ID is
DSPLOOP, it is defined at address 4B248, and the data link string specified is
G4+8%.2. 'label' is a label that is included with the datalink data in the trace
record to identify that datalink’s data. The destination is specified as a system
trace file for the issuer with a maximum size of 2000.
trsource id dsploop type data loc 4b248 5820c846
trsource id dsploop dl g4+8%.2=label
trsave id dsploop dasd to * size 2000
trsource enable id dsploop
2. This example defines, enables, and disables two trace IDs of type IO. These
trace IDs, IO1 and IO2, are put into trace set IOSET. IO1 traces I/O to devices
in the range C41-C47; up to 200 bytes of transferred data is traced. IO2 traces
I/O for USER1 to devices in the range A81-A87; up to 400 bytes of transferred
data is traced. The destination options default (because TRSAVE was not
issued) and the trace files are named IO1 and IO2 with a maximum size of 256
pages and a maximum number of 2.
trsource id io1 set ioset type io
dev c41-c47 iodata 200
trsource id io2 set ioset type io
dev a81-a87 iodata 400 user user1
trsource enable set ioset
trsource disable id io1
trsource disable id io2
1674 z/VM: CP Commands and Utilities Reference
3. This example defines, enables, and drops two trace IDs of type GT. These trace
IDs, GT1 and GT2, are put into trace set GTSET. The destinations are specified
as system trace files for user ID USER3 with a default size of 256 pages.
trsource id gt1 set gtset type gt for user user2
trsource id gt2 set gtset type gt for vmgroup gcsgroup
trsave id gt1 dasd to user3