CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

CICS TG on Windows, UNIX, or OS/2. A summary of some common errors we
encountered is given below.
ECI_ERR_NO_CICS -3
We found this error can occur because of one of the following reasons:
► CICS is not started.
► Inter-region communication (IRC) has not been started.
► The NETNAME in your EXCI connection (if using a specific connection) does
not match the value of your DFHJVPIPE variable referred to on the STDENV
DD card in the CICS TG startup JCL.
ECI_ERR_SYSTEM_ERROR -9
This error generally implies that there is a problem with the EXCI. We found this
can be caused because the CICS TG user ID can not log on to DFHIRP. This is
controlled by the DFHAPPL. and DFHAPPL. profiles in
the RACF FACILITY class. For further details refer to Chapter 6, “CICS TG
security scenarios” on page 99.
An ECI_ERR_SYSTEM_ERROR is also generated if you try to run a
transactional EXCI application (such as EciI1) and do not have a valid
CTG_RRMNAME specified.
An ECI_ERR_SYSTEM_ERROR can also be generated by security attach errors
for the mirror transaction. For further details refer to page 129 in Chapter 6.
An ECI_ERR_SYSTEM_ERROR can also be generated if the number of EXCI
pipes in use exceeds 100. For further details, refer to 7.2.3, “EXCI pipe usage” on
page 154.
ECI_ERR_RESOURCE_SHORTAGE -16
This error can occur if the CICS TG tries to allocate more pipes than there are
receive sessions defined in the CICS SESSIONS definition. In this circumstance,
you should consider configuring the RECEIVECOUNT parameter in the CICS
SESSIONS definition to be at least 100.
ECI_ERR_SECURITY_ERROR -27
This error can be caused by several different situations, including the following:
1. Surrogate security checking has failed. Check the MVS system console for
RACF errors. For details on configuring surrogate security with the CICS TG
for z/OS, refer to “Surrogate user security” on page 101.
Chapter 7. TCP connections to the Gateway daemon on z/OS 165