Problem determination for Requests coming from CICS

This topic explains how to check for problems with requests coming from CICS.

If a problem occurs, you should first do some preliminary checks to try and narrow down the cause. You can then try and analyze the problem in more detail by using tools such as trace or debugging.

Resource Adapter startup problems

If the CICS JEE Inbound Resource Adapter rar file is successfully deployed in WebSphere Application Server, “CTG5110I CICS JEE Inbound Resource Adapter is available at port 2,007” message is printed to depict the successful startup.

If a failure happens during Resource Adapter initialization, an exception is printed in the WAS SystemOut.log or SystemErr.log or trace.log based on the trace level parameters specified.

Some common possible reasons for startup failures are:
  1. InboundPort is not available - If the port specified as inboundPort in custom properties of CICS JEE Inbound Resource Adapter is already in use, Resource Adapter fails to bind to that port and throw an exception.
  2. Installed CICS Transaction Gateway version is not compatible - The installed CICS Transaction Gateway version must be at least 9.2 fix pack 1. If this pre-requisite is not met, startup of CICS JEE Inbound Resource Adapter fails with JNI Load failure: DLLVersionMismatch

Connection problems

Connection problems can happen if the configuration at TXSeries side or CICS Transaction Gateway is incorrect.

If the connection problem has occurred at the first handshake between TXSeries and CICS JEE Inbound Resource Adapter, it could be a configuration issue.
  1. Incorrect Configuration - Check whether you have specified the port and other parameters correctly at both the sides.
If connection problem happens at a later stage during running of transactions, it could be due to multiple reasons.
  1. Verify that system has enough resource to tackle the transactional workload. Try to increase the MaxSession parameter in CICS JEE Inbound Resource Adapter and SendCount in TXSeries.
  2. Increase the Data Source Connection Pool or other parameters based on the error received.