z/OS MVS Programming: Writing Transaction Programs for APPC/MVS
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


API Trace Facility

z/OS MVS Programming: Writing Transaction Programs for APPC/MVS
SA23-1397-00

Using the API trace facility, you can diagnose not only errors that occur during a specific call, but also problems with the conversation flow between the TP and its partners. Depending on the location of the partners, you might have to use the API trace facility together with tracing facilities provided for other platforms, such as OS/2.

API trace data includes entries for:
  • Parameters and values specified on calls issued for APPC/MVS and CPI-C services, and values provided on return from those calls.
  • The same diagnostic information that the APPC/MVS Error_Extract service provides for calls that return non-zero return codes.
  • Parameters and values specified on START and STOP requests for the API trace facility.

Through ATBTRACE parameters, you can start tracing for only specific TPs or users, or for many TPs, many conversations, and many users.

For more information about the API trace facility, see Diagnosing Problems with APPC/MVS TPs.

Note:

If you plan to use the programming interface for CPI Communications, read Using CPI Communications and Installing and Testing Transaction Programs. If you do not plan to use CPI Communications, continue reading with The APPC/MVS Programming Interface.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014