Resetting the Online CICS VPE Trace File

CA Ideal Trace Facility › @I$TRACE PRINT Extracting Data from the VPE Trace File › Resetting the Online CICS VPE Trace File

Resetting the Online CICS VPE Trace File

The following command erases the data in the online VPE trace file and starts writing at the beginning of the file. Use it when the VPE trace file fills up (an ASRB abend occurs). In batch, if the trace file fills up, you can rerun the job with a larger trace file.

This command has the following format:

@I$TRACE RESET

You must use the following procedure with this command.

If you are still in CA Ideal, sign off from CA Ideal, but not off from CICS.
From CICS, close and reopen the VPE trace file using the CEMT CICS Operator command against the DCT. That is:
```
CEMT S TDQ(ADRT) CLOSE
```
```
CEMT S TDQ(ADRT) OPEN
```
Sign back on to CA Ideal.
From CA Ideal, issue @I$TRACE RESET.

@I$DIALMASK Initiating a DIAL Trace

The following command produces internal diagnostics for a COMPILE of a CA Ideal program, a CATALOG of a CA Ideal dataview, or a RUN of a CA Ideal program. It also specifies which CA Ideal internal tasks or functions are logged. The command lets you log DIAL trace entries either to the VPE trace file or to a separate DIAL‑only trace file. The previous section described how to extract entries from the VPE trace file. The next section describes how to print trace information.

This command has the following format:

                            {'codes'    }
SET [COMPILE] @I$DIALMASK   {'ALL'      }
    [RUN    ]               {'ONLYcodes'}
                            {'ONLYALL'  }

Source Transport can also process this command, but do not specify COMPILE or RUN.

COMPILE

Produces internal diagnostics for a COMPILE or CATALOG.

Since an online compile is normally an asynchronous task and online asynchronous tasks cannot be traced, you should produce the DIAL trace diagnostics for a compile in batch. If a batch compile is impossible, use one of the following methods to trace the compilation:

Issue the COMPILE command with @I$SYNC. For more information about @I$SYNC, see the “Application Debugging Tools” chapter.
Turn on the global trace (@I$TRACE ON GLOBAL) and then COMPILE the program. This can quickly fill up your trace file.

Remember that both of these methods can affect system performance for the duration of the trace.

RUN

Produces internal diagnostics for a RUN. You can also trace the CREATE MODULE and GENERATE PLAN or PACKAGE using the RUN option.

codes

The DIAL trace codes for the CA Ideal tasks or functions to log. Entries are logged with the VPE trace entries to the ADRTRC file. Commonly used codes are listed on the next page. You can find a complete list in the “DIAL Trace Codes” appendix.

You can concatenate any combination of codes. For example:

SET RUN @I$DIALMASK 'RSTV'

SET COMPILE @I$DIALMASK 'BLF'

Before using this command with this option, you must activate a VPE service trace (@I$TRACE ON). See the section titled @I$TRACE-Executing a VPE Service Trace in the “CA Ideal Trace Facility” chapter.

ALL

Logs all codes. For example:

SET RUN @I$DIALMASK 'ALL'

ONLYcodes

The DIAL trace codes for the CA Ideal tasks or functions to log. In batch, these entries are always logged, without VPE trace entries, to SYSDIAL in z/OS or SYSLST in VSE. Commonly used codes are listed on the next page. You can find a complete list in the “DIAL Trace Codes” appendix.

You can concatenate any combination of codes. For example:

SET RUN @I$DIALMASK 'ONLYRSP'

ONLYALL

Logs all codes. In batch, these entries are always logged without VPE trace entries to SYSDIAL in z/OS or SYSLST in VSE. For example:

SET RUN @I$DIALMASK 'ONLYALL'

Online, ONLY has no effect. DIAL trace entries are always logged to the VPE trace file, which must first be opened with an @I$TRACE ON command.

To trace Source Transport Utility execution, use the following command syntax, omitting both the RUN and COMPILE options:

SET @I$DIALMASK 'ONLYcodes'

SET @I$DIALMASK 'ONLYALL'