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

TRACERED
1878 z/VM: CP Commands and Utilities Reference
fields a given trace entry contains. Trace entries that contain fields for
only some of the selection types you indicated, but whose values in
those fields match the values you designated, are chosen for output. A
trace entry does not have to have all the selection types you specified in
order to be chosen for output.
For example, your response to the selection criteria prompt may be the
following:
code 0c32 rdev 399 vdev 191 code 1000 0100
In this case, trace entries to be selected for output depend on the
following:
- Trace entries with code 0C32 contain both an RDEV and VDEV value.
Therefore, a trace entry of 0C32 must have an RDEV field value of
399 and a VDEV field value of 191 in order to be selected for output.
- Trace entries with code 1000 contain only an RDEV value. The VDEV
selection value does not apply in this situation. Therefore, all trace
entries of code 1000 with an RDEV field value of 399 are chosen for
output.
- Trace entries with code 0100 have neither an RDEV nor VDEV value.
Therefore, all trace entries of code 0100 are output.
8. The following guidelines apply to your responses to the prompt for selection
criteria when CP and TRSOURCE data is requested:
v If you immediately enter a null line when prompted for the selection criteria,
this indicates that no data reduction is requested. As a result, all trace
entries are selected.
v You can specify a time range only once.
9. If you own more than one set of files with different originators, you must
specify NAME fn, id for the file you want.
10. All files being processed must have been created under a z/VM environment.
11. When a new system trace file or tape is being processed, a message will be
issued to the screen indicating which file or tape is being processed.
12. When you indicate VMDBK in your response, data reduction takes place by
VMDBK address. Should you want to trace a specific user or users, you need
to find out the VMDBK address for the user in question before invoking the
TRACERED command.
13. For TIME selection criteria, the handling of a two-digit year will be interpreted
within a window of 100 years centered on the current date.
For example, if the year is 1997, the 100-year window spans from 1947 to
2046. Any two-digit year in the range 47-99 will be interpreted as 1947-1999,
and any two-digit year in the range 00-46 will be interpreted as 2000-2046.
Likewise, if the year is 2003, the 100-year window spans from 1953-2052. Any
two-digit year in the range 53-99 will be interpreted as 1953-1999, and any
two-digit year in the range 00-52 will be interpreted as 2000-2052.
14. When the output is directed to a CMS file, the XEDIT command will be invoked
automatically. You can then scroll back and forth through the merged data.
15. When processing system trace files that contain GCS trace entries, it is
advisable to use the LRECL 132 option for formatted CMS output.
16. A file of fixed length records is created when the TRSAVE subcommand
extracts CP trace data. A file of variable length records is created when the
TRSAVE subcommand extracts TRSOURCE trace data. These files need to
remain in their original fixed or variable length format for proper input to
TRACERED.