DFS3298E CICS® IPIC ERROR DURING ISC TCP/IP SESSION INITIATION RC=ipicrc TEXT=cics_rs_code USER=isc_user

Explanation

During the initiation of an ISC TCP/IP session with IBM® CICS Transaction Server for z/OS®, IMS received a capability exchange response (type X'02') that indicated an IP interconnectivity (IPIC) exception error. The session initiation failed.

The TEXT field contains text that briefly describes the meaning of the error message.

In the message text:
ipicrc
The 2-byte response code that was returned by CICS.
The possible response codes are described in the following list.
02
An exception
03
A disaster event
04
The message is not valid for CICS
05
A kernel error
06
CICS purged the error
cics_rs_code
Text of up to 12 characters that briefly describes the reason code that CICS returned to IMS for the error. For a description of the possible values of cics_rs_code, see the following table.
isc_user
The user name that is associated with the session initiation request.
The following table shows the reason codes that can be displayed in the TEXT field.
Table 1. Description of CICS reason codes that can be displayed by DFS3298E
Service code HTTP status code IPIC reason code Meaning
APPLID   X'06' In the capability exchange message was received by CICS, the server_applid or its high-level qualifier does not match APPLID and high-level qualifier of the CICS subsystem.

This error is most likely caused by a value on the CICSAPPL keyword of an ISC statement that does not match the APPLID of the remote CICS subsystem.

Correct the value of the CICSAPPL keyword on the ISC statement in the IMS Connect configuration member in the IMS.PROCLIB data set.

CICS reason text: ISCE_INVALID_APPLID
AUTOINSTALL   X'01' The CICS autoinstall function could not create the required IPCONN resource in the CICS subsystem.

The autoinstall function can fail if the name of the new IPCONN resource is the same as the name of an existing IPCONN resource.

Because the name of the IPCONN resource that is created by the autoinstall function is generated from the user ID that is specified on an IMS session initiation request, such as the /OPNDST NODE command, try initiating the session with a different user ID.

CICS reason text: AUTOINSTALL_FAILED
CAPEXRACE   X'15' Capability exchange race. The session between IMS and CICS was initiated by IMS and CICS at the same time, which created a race condition between the two capability exchange requests. Try issuing the IMS /OPNDST command again.

Try initiating the session again from either IMS or CICS.

CICS reason text: CAPEX_RACE
DFHxxxxx     API conversation error.

DFHxxxxx is the CICS API error message that was returned to IMS Connect, where xxxxx is a number, and DFH is the CICS message prefix.

This error is probably an internal error. Contact IBM Software Support.
HTTPRQST X'400'   Defined by the HTTP protocol or the TCP/IP server, indicates that the request could not be understood by the server because the syntax was malformed.

The session initiation request is probably invalid and could not be understood by the receiving subsystem.

Check that the ISC TCP/IP session initiation request is configured properly in the subsystem that is initiating the session.

If the problem persists, contact IBM Software Support.
HTTPERR   X'0B' A capability exchange response that is related to a callback connection contained an HTTP status code that indicates an error.

CICS reason text: ISCER_HTTP_ERROR
IPCONNNO   X'13' No IPCONN resource.

An attempt to acquire or release a connection for a CICS TCPIPSERVICE resource was made, but the TCPIPSERVICE resource does not have an associated IPCONN resource.

The error is probably caused by an incorrect TCPIPSERVICE or IPCONN resource definition in the CICS subsystem. Correct any errors in the resource definitions and try to initiation the session again.

CICS reason text: NO_IPCONN
IPCONNNOTFND   X'04' IPCONN not found.

An attempt to acquire or release a connection with a CICS subsystem was made, but the required IPCONN resource no longer exists or cannot be found.

CICS reason text: IPCONN_NOT_FOUND
IPCONNONEWAY   X'14' The ISC TCP/IP session requires a two-way connection, but the CICS IPCONN resource is defined to use a one-way connection.

Correct the CICS IPCONN resource definition.

CICS reason text: ISCER_ONE_WAY_IPCONN
IPCONNSTATE   X'02' Invalid IPCONN state.

An ISCO ACQUIRE_CONNECTION was issued, but failed because the CICS IPCONN resource is not in the correct state.

The state of the IPCONN resource must be INSERVICE and RELEASED.

Try to initiate the session again. If the problem persists, contact the CICS system administrator.

CICS reason text: INVALID_IPCONN_STATE
OPENERR   X'0D' Open session error.

IMS attempted to initiate an ISC TCP/IP session with CICS through IMS Connect, but the capability exchange between the IMS and CICS subsystems failed.

The following scenarios are examples of how this error might occur:
  • The IMS Connect port is stopped.
  • The value that is specified on the PORT keyword of the IPCONN resource definition in the CICS DFHCSD data set does not match the value that is specified on the ID subparameter of the CICSPORT keyword in the TCPIP statement in the IMS Connect HWSCFGxx PROCLIB member.

This error is probably caused by a configuration or definition problem.

Verify that all IMS, IMS Connect, and CICS PROCLIB members and resources are defined correctly. Correct any errors in the definition statements.

CICS reason text: SESSION_OPEN_FAILED
PARTNERSTATE   X'03' Invalid partner state.

CICS received a capability exchange request for an IPCONN resource that is in an invalid state.

The state of the IPCONN resource must be INSERVICE and not already acquired.

Try to initiate the session again. If the problem persists, contact the CICS system administrator.

CICS reason text: INVALID_PARTNER_STATE
RECOVERR   X'08' Capability exchange recovery error.

CICS received a capability exchange request that contains an unsupported isce_preferred_recovery value and no matching isce_supported_protocols flags are set to fallback to.

This error is probably an internal error. Contact IBM Software Support.

CICS reason text: ISCE_BAD_RECOV
RESPBAD   X'09' A CICS IPIC response is bad.

The callback capability exchange response that was received by CICS contains a bad response and reason code.

This error can occur during a capability exchange if the port defined on the PORT attribute in the CICS IPCONN resource definition is not also defined to IMS Connect on the ID subparameter of the CICSPORT keyword in the TCPIP statement in the IMS Connect PROCLIB configuration member.

Verify that all IMS, IMS Connect, and CICS PROCLIB members and resources are defined correctly.

CICS reason text: ISCER_BAD_RESPONSE
RESPERR   X'0A' Capability exchange response error.

The callback capability exchange response was determined to be invalid.

This error is an internal error in either IMS, IMS Connect, or CICS. Contact IBM Software Support.

CICS reason text: ISCER_ERROR
RESPTIMEOUT   X'0C' Capability exchange response timed out.

A response to a capability exchange request was not received within the timeout period specified.

Increase the CICS IPIC request timeout value (RTIMOUT) in the system profile DFHCICSC.

The RTIMOUT value is in mmss, where mm is minutes, ss is seconds. For example, to change the timeout value to 1 minute, specify: ALTER PROFILE(DFHCICSx) GROUP(IMSISCIP) RTIMOUT(0100).

Use CICS transaction CEDA to display or update the timeout value

CICS reason text: ISCER_TIMED_OUT
RQSTERR   X'05' Capability exchange request error.

The capability exchange request was determined to be invalid and was rejected by the partner CICS subsystem. IMS or IMS Connect built an incorrect capability exchange request message to initiate a session.

Contact IBM Software Support.

CICS reason text:

RQSTTIMEOUT   X'07' The CICS IPIC request timed out.

The TCPIPSERVICE transaction (CISS by default) was attached to initialize a connection for an IPCONN resource but did not receive a capability exchange request within the timeout period that is defined in its transaction profile.

Increase the CICS IPIC request timeout value (RTIMOUT) in the system profile DFHCICSC.

The RTIMOUT value is in mmss, where mm is minutes, ss is seconds. For example, to change the timeout value to 1 minute, specify: ALTER PROFILE(DFHCICSC) GROUP(IMSISCIP) RTIMOUT(0100).

Use CICS transaction CEDA to display or update the timeout value

CICS reason text: ISCE_TIMED_OUT
SECURITY   X'16' Security error. The security credentials of the caller are not acceptable to the partner system.

CICS reason text: ISCER_SECURITY_VIOLATION
SHUTDOWN   X'0E' CICS is shutting down.

A call was made to DFHISCO to acquire or initialize an IPCONN resource, but CICS was shut down before the call was completed.

Verify that CICS is active. If CICS is not active, start it.

CICS reason text: SHUTDOWN
SOCKETERR   X'18' Client socket error. The client connection is closed.

CICS reason text: ISCER_CLIENT_CONNECTION_CLOSED
SOCKETSECERR   X'19' Secondary socket error. An error occurred when an attempt was made to obtain a secondary socket.

CICS reason text: ISCER_SEC_SOCK_ERROR
SRVCCLOSED   X'0F' TCP/IP services are unavailable.

An attempt to acquire a connection failed because no TCP/IP support is available.

Start the TCP/IP service and try initiating the ISC TCP/IP session again.

CICS reason text: TCPIP_CLOSED
SRVCMISMATCH   X'10' TCPIPSERVICE mismatch.

A capability exchange request was received for an IPCONN resource that is defined to use a different TCPIPSERVICE from the TCPIPSERVICE that was used for the capability exchange.

This error can occur if the ports defined on the CICS TCPIPSERVICE and IPCONN resource definitions do not match.

Verify that all IMS, IMS Connect, and CICS PROCLIB members and resources are defined correctly. Correct any errors.

CICS reason text: TCPIPSERVICE_MISMATCH
SRVCNOTFOUND   X'11' The TCPIPSERVICE resource that is referenced by the IPCONN resource was not found in the CICS subsystem.

CICS could not acquire or release the connection because the TCPIPSERVICE resource that is referenced in the IPCONN resource definition is either not installed or was deleted.

Try to initiate the session again. If the problem persists, contact the CICS system administrator. The TCPIPSERVICE resource might need to be reinstalled and opened.

CICS reason text: TCPIPSERVICE_NOT_FOUND
SRVCNOTOPEN   X'12' The TCPIPSERVICE resource in the CICS subsystem is not open.

The CICS subsystem attempted to acquire a connection for an IPCONN resource, but the TCPIPSERVICE named in the IPCONN resource definition is not open.

Try to initiate the session again. If the problem persists, contact the CICS system administrator.

CICS reason text: TCPIPSERVICE_NOT_OPEN
SRVCUNAVAIL X'503'   Defined by the HTTP protocol or the z/OS TCP/IP server, indicates that the TCP/IP server is temporarily unavailable either because it is overloaded or down for maintenance.

Verify that the TCP/IP server is active. If the TCP/IP server is not active, start it.
SRVRERR X'500'   Defined by the HTTP protocol or the z/OS TCP/IP server, indicates that the TCP/IP server encountered an unexpected condition that prevented it from fulfilling the request.

Hypertext Transfer Protocol -- HTTP/1.1
UNKNOWN   X'63' Unknown error. This error is probably an internal error. Contact IBM Software Support.

System action

The attempt to initiate an ISC TCP/IP session with CICS fails. IMS continues processing.

System programmer response

Review the explanations of the CICS response and reason codes that were included in the DFS3298E message. For more information about the codes and the possible actions to take to correct the error, consult with your CICS support personnel.

Confirm that the following elements are configured correctly:
  • The ISC terminal in IMS, by either an ETO logon descriptor or stage-1 system definition macros such as TYPE, TERMINAL, and SUBPOOL
  • The ISC link in IMS Connect, by the ISC and RMTIMSCON statements
  • The TCPIPSERVICE and IPCONN statements in CICS

Module

DFSIPIC0