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

► Errno 163
JNI trace entry CCL6808I: CcicsECI: Authorize userid/password with
RACF. Return code = -1, errno = 163.
errno.h #define EMVSSAFEXTRERR 163 /* SAF/RACF extract
error */
Reason SURROGATE=YES and unauthorized RACF ID used
Tip: The errno diagnostic information should only be used if the return code is
not equal to 0. In the errors above, the return code is -1.
ECI_ERR_NO_CICS -3
This error can occur because:
► Inter-region communication (IRC) has not been started in the CICS region
► The EXCI CONNECTION definition is not installed in the CICS region
► The NETNAME in your EXCI connection does not match the value of the
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 communication
mechanism. In our tests, we found this could be caused by two quite different
situations:
► Security attach failure for the mirror transaction
If you are using security and the user ID flowed in the ECI request does not
have READ access to the TCICSTRN class profile controlling access to the
specified mirror transaction, then you will receive this error. If this is the case,
you will also receive the error message ICH408I in the CICS job log. For
details on configuring the required profiles, refer to “Access to the mirror
transaction, CSMI” on page 109.
► MRO bind security failure
Access to DFHIRP is controlled by the DFHAPPL. and
DFHAPPL. profiles in the RACF FACILITY class.
If you do not permit your CICS TG for z/OS address space user ID to log on to
IRP, you will receive the error seen in Example 6-14. This was captured from
a JNI trace. Details on getting this trace can be found in “JNI trace” on
page 176.
Example 6-14 JNI trace of an unauthorized link
Chapter 6. CICS TG security scenarios 129