MVS 3.8J
GTFPARM

GTFPARM -- Parameters to control GTF

TRACE=SYS,SRM,PCI,DSP                                                   00000010

Parameter in IEASYSxx

None

Notes

  1. This member is read only when the operator issues START GTF.

  2. It is not used during system initialization.

Syntax

  • Specify the TRACE keyword and its main options only on the first record.

  • The second and subsequent records should only contain "prompting" keywords.

  • An END statement or an end-of-file must follow all prompting keywords.

  • If you need to specify additional operands for the same keyword, restate the keyword and the additional operands on a subsequent record.

Parmaeters

Parameter Meaning and Use
SYS Requests comprehensive recording for six system events: I/O, SIO, SVC, program, external interruptions, and entry to recovery routines (RR).
SYSP Is similar to the SYS parameter except that GTF prompts for particular events (e.g., address of I/O device or SVC number).
SYSM Is similar to the SYS parameter except that minimal trace data are recorded for the six events.
SIO Requests comprehensive recording for system SIO operations.
SIOP Similar to the SIO parameter except that GTF prompts for the addresses of specific devices for which SIO events should be recorded.
IO Requests comprehensive recording for all non-PCI I/O interruptions.  To obtain recording of PCI interruptions, specify PCI.  Both options may be specified.
IOP Similar to the IO parameter except that GTF prompts for the addresses of specific devices for which IO interruptions should be recorded.
SVC Requests comprehensive recording for all system SVC interruptions.
SVCP Similar to the IO parameter except that GTF prompts for the specific SVC number for which interruptions should be recorded.
PI Requests comprehensive recording for all program interruptions (1-19).
PIP Similar to the PI parameter except that GTF prompts for the specific interruption codes for which data will be recorded.
EXT Requests comprehensive recording for all external interruptions.
RR Reqeusts that uses of recovery routines (FRRs and STAE/ESTAE routines) be recorded.  The trace record is generated when the recovery routine returns control to the recovery termination manager (RTM).
DSP Requests recording for the local dispatching of units of work (service request block (SRB) and TCB).
PCI Requests that PCI interruptions be recorded in the same format as other requested I/O trace records.  If specific I/O device addresses are specified through prompting records, the PCI interruptions will be recorded for the same devices.
SRM Requests a trace entry each time that the system resource manager (SRM) is invoked.
TRC Requests that traced events include those related to GTF processing itself.  If not specified, GTF-related events will be excluded from the trace output.
USR Requests that user data passed to GTF via the GTRACE macro be recorded.
END This parameter indicated the end of the prompting records.