End of support This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Using the SMDIAGxx member

Diagnostic definitions are specified by SET statements. INC and EXC statements following the SET statement identify the specific situations to be debugged.

Warnings
  • Use SMDIAGxx only if BMC Customer Support directs you to do so.
  • Use only the valid combinations listed. Otherwise, or unpredictable results can occur.

The following table describes the valid SET and INC statements that are available in the SMDIAGxx member.

SMDIAGxx SET and INC statements

SET variable

INC variable

FUNCTION

JOB

STEP

PGM

MODULE

TRACE

Y

Y

Y

Y

Y

DEBUG

N

Y

Y

Y

Y

MODTRC

N

Y

Y

Y

Y

DUMP

N

Y

Y

Y

Y

ABEND

N

N

N

N

Y

IGNORE

N

Y

Y

Y

N

 

FUNCTION, JOB, STEP, and PGM variables are not valid with the ABEND action parameter. The MODULE variable is not valid with the IGNORE action parameter. The FUNCTION variable is not valid with the MODULE action parameter.

You can use the TRACE action parameter (see Using-the-tracing-facility) instead of //PROTRACE to get an FLST/RLST trace. The action parameters specified in the SMDIAGxx member override any special JCL DD statements, such as //PROTRACE, as well as the TRACE function parameter.

The IGNORE parameter will override the // PROIGN DD statement. If the DIAG member specifies IGNORE=NO, even the presence of a //PROIGN DD statement will not prevent MainView SRM functions from being activated.

 

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