CA Datacom Tools 15.1

15.1 15.0
English

CA Ideal for CA Datacom Trace Facility

The idcm Trace Facility is a debugging aid that traces the idcm and CA IPC components executed when any command is executed in idcm.
cadts151
The 
CA Ideal™ for CA Datacom®
 Trace Facility is a debugging aid that traces the 
CA Ideal™ for CA Datacom®
 and CA IPC components executed when any command is executed in 
CA Ideal™ for CA Datacom®
.
Under certain circumstances, 
CA Ideal™ for CA Datacom®
 Technical Support requests that you run a 
CA Ideal™ for CA Datacom®
 Trace. CA Technical Support uses the trace output to identify the internal processes that precede or accompany an abend, internal errors, or unexpected results from a 
CA Ideal™ for CA Datacom®
 program.
This page contains the following topics:
 
 
Trace Facility Functionality
The 
CA Ideal™ for CA Datacom®
 Trace Facility provides the following functions:
  •  
    VPE service trace (@I$TRACE).
    This function records all 
    CA Ideal™ for CA Datacom®
     service routines called and CA IPC service macros invoked during a specified part of a 
    CA Ideal™ for CA Datacom®
     session. It generates entries for all 
    CA Ideal™ for CA Datacom®
     online and batch services requested (except those that invoke asynchronous tasks online). It includes a facility to extract and print selected entries.
  •  
    DIAL trace (@I$DIALMASK).
    DIAL stands for Debugging Interface for Assembly Language. This facility records internal diagnostics 
    CA Ideal™ for CA Datacom®
     modules executed as a result of a RUN, COMPILE, or CATALOG command or the Source Transport Utility produce.
  •  
    Object Module List command (@I$CALL ADPOBJ)
    This function provides dumps of VLS object modules.
The Object Module List is described later in this chapter. The VPE and DIAL traces are described as follows.
The following graphics illustrate the data flow of the VPE and DIAL traces under z/OS and VSE. There are significant differences between the way the traces work online and in batch. These differences are described afterward.
z/OS trace facility flow is as follows:
VPE              VPE Trace                  (Online)  Output
Trace  -------->   File  --------->  Extract   ------->  Member
                  ADRTRC              Data               OUTTRACE
                    |                   |
                    |  (Online/         |  (Batch)
                    |   Batch)          |
DIAL   -------->    |                   |
Trace               |  (Batch)          |
                 DIAL-Only File       Print File
                   SYSDIAL             AUXPRINT
VSE trace facility flow is as follows:
VPE              VPE Trace                  
Trace  -------->   File  --------->  Extract   
                  ADRTRC              Data     
                    |                   |
                    |  (Online/         |  (Batch Only)
                    |   Batch)          |
DIAL   -------->    |                   |
Trace               |  (Batch)          |
                 DIAL-Only File       System
                   SYSLST             Printer
Batch Traces
In batch, the 
CA Ideal™ for CA Datacom®
 traces work as follows:
  • The VPE service trace writes entries to the VPE trace file (installed as ADRTRC) as the batch program makes requests. Information can then be extracted from the VPE trace file selectively (for example, by the function or by the time an error occurred).
    Under z/OS, the extracted information goes to a file (installed as AUXPRINT), which you can then print or display (as any SYSOUT file) using standard operating system spooling or print facilities.
    Under VSE, the extracted information goes to the current system printer (specified in the site-assembled 
    CA Ideal™ for CA Datacom®
     Batch File Table (IDSYSFT) PSSPRT
    nn
     entries).
  • The DIAL trace writes entries for specific 
    CA Ideal™ for CA Datacom®
     internal tasks or functions to either of two places:
    • To the same trace file as the VPE trace, along with the VPE trace entries. Entries can then be extracted for printing as with the VPE trace. In this case, the VPE trace must be activated first.
    • In batch only, directly to a separate file without any VPE entries (regardless of whether the VPE trace is activated). Under z/OS, output goes to a sequential file (installed as SYSDIAL). Under VSE, output goes to a sequential file (installed as SYSLST).
Online Traces
In an online environment, the 
CA Ideal™ for CA Datacom®
 traces work as follows:
  • Both traces are available online. However, online, the separate DIAL-only trace output file is not supported. All information goes to the VPE trace file. The VPE trace must always be activated first.
    Online, there is only one VPE trace file for all 
    CA Ideal™ for CA Datacom®
     users. A trace can be local to a single user or globally include all users, but all traces using a given CICS region share the same file. As in batch, information can be extracted from the VPE trace file selectively (for example, by the function or by the time an error occurred).
  • Under z/OS you can print or display extracted information online using the 
    CA Ideal™ for CA Datacom®
     output processor. Under VSE, the trace can be activated online, but trace information can be extracted only in batch.
To minimize the degradation of the online system by traces, run them in batch whenever possible.
Trace Examples
The following examples illustrate how to run VPE service traces and DIAL traces under z/OS and VSE, in both batch and online environments. For a description of the JCL required, see the section titled JCL Requirements later in this section.
 
z/OS
 
 
Batch
 
 
Online
 
 
DIAL Trace of a RUN
(To DIAL
-
Only File)
 
PERSON 
uuu
 PSW 
ppp
SEL SYS 
sss
SET RUN FILETABLE DBFLT
nnn
SET RUN @I$DIALMASK 'ONLYALL'
RUN 
pgmname
OFF
 
DIAL Trace of a RUN
(To VPE Trace File)
 
SEL SYS 
sss
@I$TRACE ON LOCAL
SET RUN @I$DIALMASK 'ALL'
RUN 
pgmname
@I$TRACE OFF LOCAL
@I$TRACE PRINT FUNC DIL
PRINT OUT OUTTRACE DEST SYS
 
 
 xxx
 
 
DIAL Trace of a CATALOG
(To VPE Trace File)
 
PERSON 
uuu
 PSW 
ppp
SEL SYS 
sss
@I$TRACE ON LOCAL
SET COMPILE @I$DIALMASK 'F'
CATALOG DVW 
name
 VER 
nnn
@I$TRACE PRINT FUNC DIL
OFF
 
DIAL Trace of a CATALOG
(To VPE Trace File)
 
@I$TRACE ON LOCAL
SET COMPILE @I$DIALMASK 'F'
CATALOG DATAVIEW 
name
 VER
 nnn
@I$TRACE OFF LOCAL
@I$TRACE PRINT FUNC DIL
PRINT OUT OUTTRACE DEST SYS
 xxx
 
 
VPE Service Trace
(To VPE Trace File)
 
PERSON 
uuu
 PSW
 ppp
SEL SYS 
sss
@I$TRACE ON LOCAL
...
one or more 
CA Ideal™ for CA Datacom®
 commands
...
SCF/VPE
@I$TRACE PRINT FUNC SCF/VPE
OFF
 
VPE Service Trace
(To VPE Trace File)
 
@I$TRACE ON LOCAL
...
one or more 
CA Ideal™ for CA Datacom®
 commands
...
@I$TRACE OFF LOCAL
@I$TRACE PRINT USER 
uuu
 FUNC
PRINT OUT OUTTRACE DEST SYS
 xxx
 
 
VSE
 
 
Batch
 
 
Online
 
 
DIAL Trace of a RUN
(To DIAL
-
Only File)
 
PERSON 
uuu
 PSW 
ppp
SEL SYS 
sss
SET RUN FILETABLE DBFLT
nnn
SET RUN @I$DIALMASK 'ONLYALL'
RUN 
pgmname
OFF
 
DIAL Trace of a RUN
(To VPE Trace File)
 
SEL SYS 
sss
@I$TRACE ON LOCAL
SET RUN @I$DIALMASK 'ALL'
RUN 
pgmname
@I$TRACE OFF LOCAL
 
DIAL Trace of a CATALOG 
(To VPE Trace File)
 
PERSON 
uuu
 PSW 
ppp
SEL SYS 
sss
@I$TRACE ON LOCAL
SET COMPILE @I$DIALMASK 'F'
CATALOG DVW 
name
 VER 
nnn
@I$TRACE OFF LOCAL
@I$TRACE PRINT FUNC DIL
OFF
 
DIAL Trace of a CATALOG 
(To VPE Trace File)
 
@I$TRACE ON LOCAL
SET COMPILE @I$DIALMASK 'F'
CATALOG DATAVIEW 
name
 VER
 nnn
@I$TRACE OFF LOCAL
 
VPE Service Trace 
(To VPE Trace File)
 
PERSON 
uuu
 PSW
 ppp
SEL SYS 
sss
@I$TRACE ON LOCAL
...
one or more 
CA Ideal™ for CA Datacom®
 commands
...
@I$TRACE OFF
@I$TRACE PRINT FUNC SCF/VPE
OFF
 
VPE Service Trace 
(To VPE Trace File)
 
@I$TRACE ON LOCAL
...
one or more 
CA Ideal™ for CA Datacom®
 commands
...
@I$TRACE OFF LOCAL
 
Print VPE Trace File 
(From Online Trace)
 
PERSON 
uuu
 PSW 
ppp
@I$TRACE PRINT
OFF