Testing an EXEC with REXX statement TRACE R

By using the REXX statement TRACE R in your EXEC, you can see all the statements in the EXEC written to the BBI-SS PAS Journal and all the TSO variables resolved as the EXEC executes.

This feature is useful if you want to insure that your TSO variables are being resolved as you expected. For a complete discussion about using TRACE R to debug your REXX EXECs, see the IBM documentation TSO/E: REXX/MVS User’s Guide.

Related topic

Testing-EXECs

Enter the following statement at the line of the EXEC where you want to begin this test:

TRACE R

For example, if you were to schedule an EXEC called CALLRSTX and pass two parameters to it, type the following command at any COMMAND line:

%CALLRSTX USER1 DETAIL

The following example shows the substitution that is logged to the Journal:

14:59:24  EM0025I  FOLLOWING MSG ISSUED FOR EXEC .. CALLRSTX ..
14:59:24       3 *-* ARG NAME PARM1 DETAIL GARBAGE
14:59:24         >>>   'CALLRSTX'
14:59:24         >>>   'USER1'
14:59:24         >>>   'DETAIL'
14:59:24       5 *-* /* DISPLAY THE INPUT PARAMETERS */
14:59:24       6 *-* IMFEXEC MSG 'PARM1 =' PARM1
14:59:24         >>>   "IMFEXEC MSG PARM1 = USER1"
14:59:24  PARM1 = USER1
14:59:25       7 *-* IMFEXEC MSG 'DETAIL =' DETAIL
14:59:25         >>>   "IMFEXEC MSG DETAIL = DETAIL"
14:59:25  DETAIL = DETAIL

In this BBI-SS PAS Journal entry, you can see the substitution for the ARG statement where the values you used to schedule the EXEC are passed to the ARG statement at line 3). Line 5 shows a comment from the REXX EXEC and lines 6 and 7 show the actual substitution of the variables.

 

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