Other tracing methods

GDDM V3R2 Diagnosis

Other tracing methods

GDDM V3R2 Diagnosis
SC33-0870-01

--------------- Product-sensitive programming interface ----------------

This topic has described how to use GDDM tracing by means of TRCESTR statements in external defaults files. You can also use TRCESTR statements for GDDM tracing in the following ways:

Specify ADMMDFT TRCESTR statements in the source of an external defaults module. (How to create such a module is described in the GDDM System Customization and Administration book). This module is called:
- ADMADFC under CICS
- ADMADFI under IMS
- ADMADFT under TSO (and for the TSO Print Utility)
- ADMADFV under VM
- ADMADFD under VSE.
In your application program, include calls to ESSUDS, specifying a source-format UDS for the ADMMDFT TRCESTR statements.
The ESSUDS statement is described in the GDDM Base Application Programming Reference book.
In your application program, include calls to ESEUDS, specifying an encoded UDS for the ADMMDFT TRCESTR statements.
The ESEUDS statement is described in the GDDM Base Application Programming Reference book.
In your application program, include calls to SPINIT, specifying in the systems programmer interface block (SPIB) an encoded UDS for the ADMMDFT TRCESTR statements.
The SPINIT statement and the format of the SPIB are described in the GDDM Base Application Programming Reference book.

Note: A single trace statement in an application call must conform to the syntax for a complete program. For example, all parts of an IF THEN ELSE statement must be within a single application call. However, a trace specification can be built up from any number of separate application calls; these are appended to the trace program formed from an external file, if there is one.

There are several ways to turn on GDDM trace facilities that involve changing the value of the trace control word that is held internally by GDDM. The trace control word is a fullword integer that defines the kind of trace to be produced. If you do not specify it, its value is 0 (resulting in no trace activity). Other values for the trace control word are described under "The FSTRCE statement" in topic 2.23.

To change the trace control word for any GDDM utility or for an application program, do one of the following:

Specify the ADMMDFT TRACE value in a source-format defaults file. (The ADMMDFT macro is described in the GDDM System Customization and Administration book.
Source-format defaults files are normally available only under TSO or VM systems. However, modified versions of this mechanism can also be used under CICS or VSE.
Specify the ADMMDFT TRACE value in an external defaults module.

To change the trace control word from an application program:

Include calls to FSTRCE, specifying the trace value as a parameter. This is described under "The FSTRCE statement" in topic 2.23.
Include calls to ESSUDS, ESEUDS, or SPINIT, specifying a source-format UDS for the ADMMDFT TRACE default.

Notices | Terms of use | Support | Contact z/OS