Example 1: Tracing SMP/E messages

Suppose that a problem occurred when you ran the following SMP/E commands:
SET      BDY(MVSTST1)       /* Process MVSTST1 tgt zone.  */.
APPLY    S(USR0001)         /* Apply user modification.   */.
Because the problem appeared to be in SMP/E and not in the USERMOD, you decided to report it to IBM®. To help IBM determine the cause of the problem, you should also rerun the job with the message trace on. You can use the following commands:
SET      BDY(MVSTST1)       /* Process MVSTST1 tgt zone.  */.
DEBUG    MSGMODID(ON)       /* Start message trace.       */.
APPLY    S(USR0001)         /* Apply user modification.   */.
DEBUG    MSGMODID(OFF)      /* Stop message trace.        */.
When you run this job, SMP/E precedes all messages for the APPLY command with the name and offset of the issuing module. This stops when the second DEBUG command is processed.
Note: The second DEBUG command is not required if no further SMP/E commands are to be traced. It is used in this example only to show that the trace can be turned on and off.