XA interface problem determination
When an error is detected during an XA request from the TM, the application program may not be able to get the error code from the TM. If your program abends, or gets a cryptic return code from the TP monitor or the TM, you should check the First Failure Service Log, which reports XA error information when diagnostic level 3 or greater is in effect.
You should also consult the console message, TM error file, or other product-specific information about the external transaction processing software that you are using.
The database manager writes all XA-specific errors to
the First
Failure Service Log with SQLCODE -998 (transaction or heuristic errors)
and
the appropriate reason codes. Following are some of the more common
errors:
- Invalid syntax in the xa_open string.
- Failure to connect
to the database specified in the open string as a result
of one of the following:
- The database has not been cataloged.
- The database has not been started.
- The server application's user name or password is not authorized to connect to the database.
- Communications error.