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

TRSAVE
Examples
Responses
amount of frames is allocated. When the number of FRAMES specified on
the TRSAVE command for a DEFERIO traceid trace is greater than 512,
informational messages will be issued to document the progress of
obtaining the frames.
If a large number of frames are specified, then it may take some time for
the TRSOURCE DISABLE command to complete (and for CP trace table
recording data to be written) because at that time all of the frames must be
written to DASD or to TAPE. When the number of frames to be written out
for a DEFERIO traceid trace is greater than 3, informational messages will
be issued to document the progress of writing the frames.
Because the issuing virtual machine will be in 'command wait' until the
command completes, you should not enter the TRSOURCE ENABLE or
TRSOURCE DISABLE commands from a virtual machine that may be
adversely affected by command wait, such as a server virtual machine, a
secondary virtual machine, or a PROP virtual machine.
e. When a DEFERIO trace is eventually recorded on DASD, the SIZE and
KEEP operands affect the size and number of trace files that are kept. You
should specify a combination of SIZE and KEEP that is equivalent to the
number specified for FRAMES. That is, SIZE * KEEP = FRAMES.
f. If the system terminates with a DEFERIO trace active, then no data is
recorded on DASD or TAPE for that trace. However, the trace data can be
extracted from a CP dump.
v To record system trace table entries on DASD and specify USERA as the file
owner, enter trsave for cp on dasd to usera.
v To turn off TRSAVE for CP, enter trsave for cp off.
v To turn on TRSAVE for the trace defined by TRSOURCE ID DEBUG, save the
recorded data in a file named FILEB, and allow DUSER to process the files,
enter trsave for id debug dasd to duser name fileb.
v To use in-storage wrap for the same traceid so that data is not written to DASD
until the traceid is disabled, enter trsave for id debug deferio frames 1000
size 500 keep 2.
Response 1:
For CP tracing:
1670 z/VM: CP Commands and Utilities Reference
{ started }
TRSAVE function { completed}[: nnnn files purged]
{ canceled }[: nnnn files purged]
nnnn
is the number of trace files that have been purged during the time the trace
service tool function was active because of the wrapping of the keep limit.
When the keep limit is reached, the oldest file is purged. If the response states
that 9999 files were purged, it is possible that more than 9999 files were
purged.
You receive this when you enter trsave for cp and the TRSAVE command is
started, completed, or canceled. If you are not logged on, the completed and
canceled responses are sent to the system operator.