27.12.2012 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

TRACERED<br />

Oper<strong>and</strong>s<br />

Options<br />

1874 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong><br />

id specifies the primary input to TRACERED as a system trace file containing<br />

<strong>CP</strong>TRACE or TRSOURCE data. The id oper<strong>and</strong> is a spool ID, a decimal<br />

number from 1 to 9999.<br />

NAME<br />

specifies the primary input to TRACERED from one or more files containing<br />

trace data collected using SET <strong>CP</strong>TRACE or TRSOURCE comm<strong>and</strong>s. You may<br />

identify files by file name, origin ID, <strong>and</strong> spool ID. Trace file names are assigned<br />

by the TRSOURCE <strong>and</strong> TRSAVE comm<strong>and</strong>s. Within a set of traces, you may<br />

select trace data for a particular virtual machine by specifying an origin user ID.<br />

Further selectivity is allowed by selecting individual trace files by spool ID. The<br />

fn oper<strong>and</strong> specifies the file name assigned by the TRSAVE or TRSOURCE<br />

comm<strong>and</strong>. The ORIG userid oper<strong>and</strong> identifies, for guest type traces, files<br />

containing an individual virtual machine’s trace data. This enables an individual<br />

member of a <strong>VM</strong>GROUP trace to be specified on the TRACERED comm<strong>and</strong><br />

line. The id oper<strong>and</strong> identifies an individual system trace file created with file<br />

name fn, <strong>and</strong> it is specified as a spool ID, a decimal number from 1 to 9999.<br />

A total of five system trace files, CMS files, or both can be merged including<br />

only one <strong>CP</strong> TRACE data file. The output is merged by time-of-day <strong>and</strong><br />

formatted as it is written to a CMS file or the virtual printer as designated by this<br />

comm<strong>and</strong>.<br />

DEV vdev<br />

specifies the primary input to TRACERED as a tape containing <strong>CP</strong> trace table<br />

data at virtual device address vdev. See z/<strong>VM</strong>: CMS <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong><br />

<strong>Reference</strong> for a list of supported virtual tape devices.<br />

TAPn<br />

specifies the primary input to TRACERED as a tape containing <strong>CP</strong> trace table<br />

data at symbolic tape address TAPn. See the z/<strong>VM</strong>: CMS <strong>Comm<strong>and</strong>s</strong> <strong>and</strong><br />

<strong>Utilities</strong> <strong>Reference</strong> for a list of supported TAPn values.<br />

PRINT<br />

designates that the output of the TRACERED comm<strong>and</strong> goes to your virtual<br />

printer. This is the system default.<br />

CMS<br />

indicates that the output of the TRACERED comm<strong>and</strong> should be directed to a<br />

CMS file of the file name, file type, <strong>and</strong> file mode you specify. If you do not<br />

specify a file type, the default is <strong>CP</strong>TRACE. If you do not specify a file mode,<br />

the default is A. If you specify this keyword, you will be put into XEDIT when the<br />

comm<strong>and</strong> completes successfully.<br />

GTRACE<br />

specifies that the output will be in the form of an OS QSAM file. Only guest<br />

virtual machine recorded trace events created by TRSOURCE in either BLOCK<br />

mode or EVENT mode are output to this file.<br />

FORMAT<br />

specifies that each selected trace entry should appear in a long format. Three<br />

lines per trace entry are formatted for <strong>CP</strong> trace table entries. The number of<br />

lines of output for TRSOURCE recorded entries is determined by a formatting<br />

routine based on the length of the trace record <strong>and</strong> the output LRECL value.<br />

When the formatting routine is not supplied, the data is in hexadecimal form.<br />

The difference between HEX <strong>and</strong> FORMAT processing is left to the exit routine

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!