Using OPERTUNE diagnostic tools

This topic describes the diagnostic tools available with OPERTUNE.

Enabling OPERTUNE dumps

If you want OPERTUNE to provide a DUMP when an abend occurs in the ISPF dialogs, follow these steps:

Select option 0.7 from the main ISPF menu and set ENBLDUMP on.
Ensure that your logon procedure has a SYSUDUMP DD statement specified, or use the TSO ALLOC command when the abend occurs.

Examples

Output is sent to SYSOUT X:

TSO ALLOC FI(SYSUDUMP) CLASS(X)

Output is sent to a pre-allocated data set:

TSO ALLOC FI(SYSUDUMP) DSN(‘HLQ.SYSUDUMP’) OLD

If an abend occurs in the OPERTUNE ISPF dialogs, a panel is displayed that summarizes the following information about the abend:

load module
CSECT
password
save area flow

Record this information and supply it to the OPERTUNE BMC Support representative.

In addition, OPERTUNE allows you to perform the following tasks:

recover without a DUMP
terminate with a DUMP
terminate without a DUMP

Unless the problem has been reported, you should request to terminate with a DUMP.

Using the audit log

The started task procedure for OPERTUNE has an optional audit log for recording all commands sent to subsystems and all responses received. The audit log is activated by specifying the DDTLOG DD statement (the OPERTUNE started task procedure is distributed with the audit log active).

The log is written to SYSOUT but, if you want to write the audit log to DASD, you can pre-allocate a data set with the following attributes: LRECL=121, RECFM=FB, DSORG=PS. If you allocate the data set in the OPERTUNE procedure with DISP=MOD, you must periodically check and empty the data set to prevent it from filling up. If you specify DISP=OLD, you should copy the data set each time OPERTUNE is terminated.

If you want to write the audit log to a data set, specify DCB=BUFNO=1 on the DD statement to prevent buffering from occurring. If you do not make this specification, you will be unable to view the latest OPERTUNE logged changes through the ISPF Browse option. In addition, if you perform an IPL on the MVS system while OPERTUNE is still up, some OPERTUNE changes may not be logged to the data set.

Using the trace facility

BMC Support might ask you to provide additional diagnostic trace information. OPERTUNE has a built-in trace facility that provides detailed trace information about the commands issued to subsystems and the responses received. Activate this facility by specifying a DDTTRACE DD statement (to SYSOUT) in the OPERTUNE started task procedure or in the ISPF dialogs, by adding the DD statement to your logon procedure. This facility is not automatically placed in the default procedure because of the overhead involved with its use.

If you want to write the trace to DASD, preallocate a data set with the following attributes: DISP=OLD, LRECL=121, RECFM=FB, DSORG=PS. Because this data set is activated for only brief time periods at the request of a BMC representative, be sure that it is large enough to hold all trace data.

Applying maintenance with zaps

Use member DDTZAP in the CNTL library to apply zaps and to track maintenance.