Methods of Invoking the ATBTRACE REXX Exec

To start, stop, or list API tracing activity, you may invoke the ATBTRACE REXX exec:

In the TSO/E foreground, explicitly or implicitly, through the EXEC command
In MVS batch, through JCL
Through the JCL in an APPC/MVS TP profile
From a high-level language program.

Which method you choose depends on the circumstances. You do not need to issue all requests through the same method; for example, you can start API tracing through JCL, but stop that tracing activity by issuing the TSO/E EXEC command. Some Suggestions for ATBTRACE START Requests... might help you decide which methods to use; individual descriptions of t he START, STOP, and LIST requests contain additional examples of circumstances for selecting a particular invocation method.

The following sections contain APPC/MVS-specific requirements and examples for each method of invoking the ATBTRACE REXX exec. Depending on the method, you might have to refer to additional sources:

z/OS TSO/E REXX User's Guide for general information about invoking execs in the foreground, in batch, and from a high-level language program.
z/OS TSO/E REXX Reference for general programming requirements (such as register contents on entry) for invoking execs in batch and from programs.
z/OS MVS Planning: APPC/MVS Management for information about TP profile files.
z/OS MVS JCL Reference for information about JCL.