z/OS MVS System Messages, Vol 3 (ASB-BPX)
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


ATB498I

z/OS MVS System Messages, Vol 3 (ASB-BPX)
SA38-0670-00

ATB498I
API TRACES STARTED WITH THE DATA SET dsname IN USE BY user WERE STOPPED BECAUSE OF A SEVERE INTERNAL ERROR

Explanation

The system encountered a severe error while processing an application program interface (API) trace record, and stopped the trace. Any API trace entries that were collected but not written to the data set might be lost. The error might be an I/O error, or an error in APPC/MVS.

In the message text:
dsname
The data set for which all the API traces were stopped.
user
The user ID under which the ATBTRACE START request was issued for this data set.

System action

The system stops all active API traces associated with the data set. For an I/O error, the system issues messages with the prefix AHL, IEC, or IOS, along with this message. If no AHL, IEC, or IOS messages accompany ATB498I, the error is in APPC/MVS, and the system issues a dump of the APPC address space.

Operator response

Provide the system programmer with the dump or the I/O-related error messages. If possible, notify the user of the data set that API tracing activity has stopped.

System programmer response

If an I/O error was encountered, follow the instructions for the accompanying AHL, IEC, or IOS messages to correct the problem. Otherwise, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM® Support Center, and provide the dump.

Programmer response

If API tracing is still required, submit the ATBTRACE START request again. If an I/O error was encountered for the data set, allocate another data set on a different device and resubmit the ATBTRACE START request, specifying the name of the new data set.

Module

ATBVSTW

Source

APPC/MVS

Routing Code

2

Descriptor Code

4

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014