Diagnosing problems

Errors might come from various sources that are involved in the transaction of the message request or response. You can configure the application server to log and trace the component-specific information, and IMS™ TM resource adapter also generate messages from Java™ exceptions.

Diagnosing IVP failures
If an error occurs when you run the IMS TM resource adapter IVP, first check for information in WebSphere® Application Server logs.
Diagnosing problems accessing IMS from Java applications
If you are unable to access IMS from your Java application, verify that IMS TM resource adapter is properly set up and configured, that IMS Connect and IMS are active, and that you can access the host system by using the ping command.
Diagnosing problems with callout requests
Callout request errors are often related to the execution timeout setting, incorrect or corrupted callout messages, or network failures.
Java exceptions that involve output messages
If any errors occur when the IMS TM resource adapter passes the message through IMS Connect to IMS, and as IMS processes this transaction and attempts to return the output, the Java client receives an exception.
Logging and tracing IMS TM resource adapter information
Configure the logging and tracing setting in WebSphere Application Server to ensure messages are logged, and diagnostic trace information is recorded for the IMS TM resource adapter.
IMS TM resource adapter messages and exceptions
IMS TM resource adapter messages are Java exceptions that are thrown by the IMS TM resource adapter itself or by class libraries that it uses (such as the Java class libraries), and have the prefix of ICO.
Other exceptions and error messages
You might encounter errors from IMS Connect, or from WebSphere Application Server, as it catches the error messages and exceptions that are thrown by the IMS TM resource adapter or the class libraries used by the IMS TM resource adapter.