Obtaining traces

Enhanced call tracing can be a valuable tools for solving application program problems.For more information, see Using AR/CTL operational services.

The following DD statements may be useful if you include them in the application program job step JCL:

ASMTRACE DD

If a problem occurs during AR/CTL processing and an application program is using an ASAM data set or a GSAM data set that AR/CTL is replacing with ASAM), the BMC Software technical support analyst may ask you to include the ASMTRACE DD statement to define the ASAM trace data set. The following shows how the data set should be allocated:

//ASMTRACE  DD DSN=data.set.name,DISP=(NEW,CATLG,CATLG),LRECL=4096,
//             RECFM=FB,BLKSIZE=16384
RMTTRACE DD

If a problem occurs during AR/CTL processing and the application program is using a data set through remote VSAM access services, the BMC Software technical support analyst may ask you to include the RMTTRACE DD statement to define the remote VSAM access trace data set. The following shows how the data set should be allocated:

//RMTTRACE  DD DSN=data.set.name,DISP=(NEW,CATLG,CATLG),LRECL=4096,
//             RECFM=FB,BLKSIZE=16384

The block size can be any even multiple of 4096.

VSMTRACE DD

If a problem occurs during AR/CTL processing and the application program is using a data set through local VSAM access services, the BMC Software technical support analyst may ask you to include the VSMTRACE DD statement to define the local VSAM access trace data set. The following shows how the data set should be allocated:

//VSMTRACE  DD DSN=data.set.name,DISP=(NEW,CATLG,CATLG),LRECL=4096,
//             RECFM=FB,BLKSIZE=16384

The block size can be any even multiple of 4096.




This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments