Additional trace options


You can include the following parameters in the SMMSYSxx PARMLIB member to control tracing activity:

Parameter

Default

Description

MODTRCDD=ddname

PROMTRCE

Activates BMC AMI Storage module entry/exit tracing

TRACEDD=ddname

PROTRACE

Activates standard BMC AMI Storage tracing (as in TRACE=job name)

IGNOREDD=ddname

PROIGN

Deactivates BMC AMI Storage for the duration of the job step

DUMPDD=ddname

PRODUMP

Produces a SYS1.DUMPxx dump if BMC AMI Storage abends

DIAGMSDD=ddname

PRO$D$M$

Activates WTO message tracing

If you include in a job step the DD name that is specified in the tracing DD parameter, all BMC AMI Storage activity for the job step is traced or not traced (if you specify IGNOREDD).

TRACEDD is the same trace as produced by the TRACE parameter in the function definition in SMFUNCxx. IGNOREDD can be useful when a quick override to a BMC AMI Storage rule is needed. The other three tracing DD parameters are primarily for use by BMC personnel in resolving problems.

The BMC AMI Storage connections are not invoked into the operating system early enough for the following functions to be displayed in the DD name-activated trace:

  • DSNCHECK
  • SMSACSDC
  • SMSACSMC
  • SMSACSSC
  • SMSACSSG
  • SMSACSTE

You can use the TRACE=YES parameter in the SMDIAGxx member to activate tracing for these or any other functions.

Sample JCL statements are as follows:

//PROMTRCE DD DUMMY
//PROIGN DD DUMMY
//PRO$D$M$ DD DUMMY
//PROTRACE DD DUMMY
//PRODUMP DD DUMMY

Important

When using one of the BMC AMI Storage trace JCL statements, you should insert the DD statement near the beginning of the job step. For better performance, BMC AMI Storage limits the number of ddnames it will search to locate the presence of a trace DD. (For more information about setting the TRCDD limit, see SET command.)

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*