Debug parameters

You have the option of logging the XA interface in openUTM for test purposes. The RMXA start parameter DEBUG= is available for this purpose. This parameter must be passed before the other RMXA start parameters. It is not passed to the database system.

It is recommended that you only use this function for test purposes, as the output can become very extensive. Every transaction is logged in the task, irrespective of whether there is any access to the database.

The DEBUG= parameter has the following format:

.RMXA DEBUG={ YES | ALL },OUTPUT={ SYSOUT | FILE }

Explanation

DEBUG=	Activates the debug function. Use DEBUG= as the first RMXA start parameter.
YES	Logs the individual XA calls and, for each call, the service number the transaction counter the return value
ALL	In addition to the values logged with DEBUG=YES, the status values and the XID are also logged.
OUTPUT= SYSOUT FILE	Specifies the output destination. The log is written to SYSOUT. Output is sent to a file. The file name has one of the following formats: KDC.TRC.XA.appliname.tsn  Name of the application, up to 8 characters in length. tsn TSN of the UTM task (4-digit)

Alternatively, a file can be assigned using the link name KDCXA.

Example:

/SET-FILE-LINK LINK-NAME=KDCXA,FILE-NAME=XA-DEBUG.BSP.01

You can enable or disable logging of the XA interface during execution of the application using the administration functions. To do this, use the program interface, the administration tools WinAdmin/WebAdmin or the administration command KDCDIAG XA-DEBUG=. For details, refer to the openUTM manual “Administering Applications”.