You can also use the Start Trace (STRTRC) command to perform traces. The STRTRC command is more flexible and less intrusive than the Trace Job (TRCJOB) command. It allows tracing across multiple jobs and shows more in-depth details about the module flow.
As the trace records are generated, the records are stored in an internal trace storage area that is identified by a session ID. When the trace is ended using End Trace (ENDTRC), the trace records are placed in a user-specified library as a set of database files. These files can then be written to a spooled printer file (QPSRVTRCJ) or directed to a database output file by issuing the PRTTRC.
A sample trace scenario is as follows:
STRTRC SSNID(DRDATRACE) JOB((*ALL/QUSER/QRWTSRVR)) MAXSTG(160000) TRCFULL(*STOPTRC)
Run the failing DRDA® scenario:
ENDTRC SSNID(DRDATRACE) DTALIB(TRACELIB) PRTTRC DTAMBR(DRDATRACE) DTALIB(TRACELIB)