Stopping Trace Activity

Through the ATBTRACE REXX exec, you may stop all active API traces for a particular data set. Depending on the way your installation chose to set up API trace data sets and restrict their use, you might be stopping traces started by other programmers when you issue a STOP request. Before issuing the STOP request, consider requesting a list of active traces for this data set, and reviewing the results to determine whether you might be adversely affecting the work of others. Keep in mind that, after an error occurs, the longer you wait to stop tracing, the greater the risk of losing pertinent trace data through wrapping.

Your installation might restrict the use of not only API trace data sets, but also APPC/MVS LUs and TPs. To successfully issue a STOP request, you must either:

Have issued the first ATBTRACE START request for this data set, or
Have the appropriate access to the security profile for the ATBTRACE resource for all the LUs and TPs for which APPC/MVS is storing trace data in this data set.

Otherwise, APPC/MVS rejects the STOP request, issuing an ATB6xxxxI message that states the security violation.

When it successfully processes a STOP request, APPC/MVS returns message ATB60036I to the issuer of the request to indicate successful completion, and writes ATB60052I in the specified data set. This message contains a user ID and time stamp to indicate who stopped the traces for this data set, and at what time.

In some cases, APPC/MVS must delay the processing of a STOP request, usually because of extensive I/O activity. If a delay is necessary, APPC/MVS issues message ATB60024I to indicate that the STOP request is queued for processing. To determine when the STOP request has completed, issue an ATBTRACE LIST request for this data set; if the response to the LIST request is ATB60047, the STOP request is still pending.

If errors occur during STOP processing, APPC/MVS issues various ATB6xxxxI messages to inform the issuer of the STOP request.