DFHIS1007    date time applid Unable to acquire IPCONN ipconn. Failure to open session to hostname, port portnumber.

Explanation

During processing of an acquire for IPCONN ipconn module DFHISCO of the IP interconnectivity (IS) domain failed to open a Web session with host hostname on port portnumber. This is probably because there is no TCPIPSERVICE in a partner CICS open on port portnumber at host hostname

It might also be because the HOST is specified either as an explicit IPv6 address or a host name that will resolve to an IPv6 address, but the TCP/IP stack being used does not support IPv6.

For IP interconnectivity to be successful when using IPv6 addresses, the TCP/IP stack for both the local and remote regions must support IPv6.

If this is a connection to an IPIC HA cluster then the failure may result from a mismatch in the security attributes in the local IPCONN and the remote TCPIPSERVICE.

System action

An exception trace is written by IS domain and the task in progress is abended.

User response

Check that the hostname and port are correct and ensure that there is a partner CICS active at the given host with a TCPIPSERVICE with protocol IPIC open on the given port. Reissue SET IPCONN ACQUIRED if required.

If there is still a problem and IPv6 addresses are being used, check that the TCP/IP stack supports IPv6. See the z/OS Communications Server IP Diagnosis Guide on using Netstat to find information about the stack. DFHISCO

For an IPIC HA client, check the SSL setting in the local IPCONN against that in one of the HA server regions' generic TCPIPSERVICE and correct if it does not match the server setting. All the server regions in an HA cluster must use the same generic TCPIPSERVICE settings.

Module

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. ipconn
  5. hostname
  6. portnumber

Destination

CISO



DFHIS1007.html | Timestamp icon Last updated: Sunday, 4 June 2017