For example, the request might flow from your CICS® region, across TCP/IP to a PPC gateway, then from the PPC gateway through an SNA network to arrive in a mainframe CICS/ESA system where it is to be run.
Type of request | Local CICS messages (console.msg and CSMT.out) | PPC Gateway server messages | SNA link trace | Remote system's message |
---|---|---|---|---|
TCP/IP intersystem request with CICS family TCP/IP or IPIC support over TCP/IP | Yes | Yes | ||
PPC Gateway server configuration | Yes | Yes | ||
PPC Gateway server/SNA intersystem request | Yes | Yes | Yes | Yes |
Local SNA intersystem request | Yes | Yes | Yes |
PPC Gateway server messages are described in PPC Gateway server message descriptions.
It is possible that several components have reported the error. However, it is usually the component that initially detects the error that gives the most precise diagnostics. Refer to the message descriptions because they might give you the exact cause of the error.
If the messages do not identify the problem, try turning on the trace in each component and rerunning the failing request. Traces show the calls and responses that are being passed between the different components that might highlight a bad parameter or return code. They tend to be designed for developers of the product and so are not easy to read without the product design information. However, the trace will tell you whether the request even reached a particular component. If you find that the request failed before reaching the remote system, concentrate your suspicions around the component that rejected the request. Check the configuration of this component. Also refer to the information that is given in Common intercommunication errors because it might describe the failure that you are seeing.
If you still cannot determine what is wrong, refer to Getting further help because you need help from the service representative.