Troubleshooting Intersystem communication errors

This topic describes you can troubleshoot intersystem errors in a CICS environment.

The following topics contains information about problem determination in an intercommunication environment. It is provided for CICS® users who are new to SNA.

The following reference section provides you information about problem determination in an intercommunication environment:

  • The steps to take to track down and solve an intersystem problem
  • Common intercommunication problems
  • CICS intercommunication error codes that appear in CICS messages
  • PPC Gateway server problem determination procedures
If your errors are related to:
  • For commonly observed communication errors in intersystem communication setup, see Common intercommunication errors
  • Some CICS error messages contain communications error primaryCode/secondaryCode where primaryCode is the primary error code, and secondaryCode is the secondary error code. The following list shows the primary and secondary error codes for problem determination when you get a CICS communications error message that contains these codes, CICS error codes.
Note: If you have configured a region on Linux to communicate with CICS TS using local_sna as the protocol (the region is configured with a SNA listener), you might see the following error in the region console after the intersystem communication request: 
ERZ058134E/0035 02/21/14 12:14:53.339475000 CS7LSNA2 
26451/0006: Unable to contact the SNAplus server.  Primary return code 11f0, secondary return code 26.

You can resolve the issue by setting the LD_PRELOAD=/usr/lib/libpLiS.so variable in the region's environment file and then cold starting the region. You can now attempt the intersystem communication request.

If you see the following warning messages in your region console file, you could be running out of free ports on your system:
1 29823 14/12/12-18:41:52.907878 6c1c2c57 W binding socket name: errno:98

Symptom: Socket bind warning with errno:98 (on UNIX and Linux) or errno:10060 (on Windows) with ppc_tcp protocol.

Contact your system administrator to resolve this issue by increasing the local port range and set the following environment variables to indicate the minimum and maximum ports available for the ppc_tcp protocol:
  • ENCINA_PPC_PORT_LOW=<set this to the minimum valid local port on the box>
  • ENCINA_PPC_PORT_HIGH=<set this to the maximum valid local port on the box>
For example:
ENCINA_PPC_PORT_LOW=15000
ENCINA_PPC_PORT_HIGH=62000
Note: By default, the minimum and maximum port values used by ppc_tcp protocol are 1024 and 5000 respectively.