If you are experiencing TCP/IP connectivity problems, read
the following information to find out how to diagnose the problem.
Before you begin
Ensure that TCP/IP services are active by specifying TCPIP=YES
as a system initialization parameter. Ensure that your TCP/IP resource
definitions are defined, installed and open. For more information
about configuring TCP/IP, see
Using TCP/IP in a CICS region.
About this task
You might be having problems either because you have changed
the HOST attribute in your resources to allow IPv6 traffic, or you
might have a problem and none of your configuration settings have
changed, for example, because there have been external changes that
have affected your settings. Investigate the source region and target
region to find out why you have problems connecting.
Procedure
- For each region, determine if you are operating in a single-mode
(IPv4) environment or a dual-mode (IPv4 and IPv6) environment. Common problems related to IPv6 are because an environment does
not support IPv6 and an IPv6 address has been used to attempt a connection
to that environment. The figure shows that two dual-mode CICS® TS 4.1 environments
can communicate using either IPv4 or IPv6 addressing. A single-mode CICS TS 4.1 environment
is also connected, but can communicate using IPv4 only.For more information about
single and dual-mode environments, see Understanding IPv6 and CICS.
The following problems are examples of messages received when there
is a mismatch of IPv4 and IPv6 environments:
- If the TCPIPSERVICE definition in the listening CICS region specifies an IPv6 address
in the HOST attribute (or a hostname that resolves
to an IPv6 address) and either CICS region
is operating in a single mode environment, the listening CICS region might receive a DFHAM4907W message "Opening
TCPIPSERVICE XXXX has failed because the IP address is not known".
One of the situations when this message is issued is because a region
operating in a single-mode environment does not have IPv6 capability.
- If a CICS region
operating in a dual-mode environment issues a WEB OPEN command,
specifying an IPv6 address (or a hostname that
resolves to an IPv6 address) to a listening CICS region that is operating in a single-mode
environment, the CICS region
issuing the command might receive a NOTFND error code with a RESP2
value of 20 (host name is not resolved by name server or the format
of the host option is incorrect). This message can be issued because
the dual-mode environment has attempted to connect using IPv6 and
the single-mode region does not have IPv6 capability.
- Check that you have not explicitly specified IPv6 address
information in the HOST option of your resources (or a hostname that
resolves to an IPv6 address), unless you know that you operate in
a CICS TS 4.1 dual-mode
environment, and that any remote regions you want to connect to CICS TS 4.1 also
operate dual-mode environments. You might receive message DFHIS1007 if
an invalid attempt was made to use an IPv6 address.
- Check that an attempt to install and open the TCPIPSERVICE
resource was successful. If message DFHSO0110 is
issued, it might be that an IPv6 address or a hostname that
resolves to an IPv6 address has been specified, and there is no dual-mode
capability to support the request.
- If the TCPIPSERVICE resource opens successfully, check
message DFHSO0107, which returns the IP address that
was used to connect. This will give you more information
on the type of address used.
- Check that the address you entered is being displayed
in the format that you expect. If you have specified a
low IPv6 address, that is, the address has leading zeros in the first
six or more segments, CICS stores
and displays the IPv6 address in IPv4 format. Here are some examples
of how CICS displays low IPv6
addresses:
Table 1. How CICS handles
valid low IPv6 addresses| Specified valid IPv6 address |
How CICS stores
and displays the address |
| ::9 |
0.0.0.9 |
| ::10 |
0.0.0.16 |
| ::10A |
0.0.0.10 |
| ::ABCD |
0.0.171.205 |
| ::FFFF |
0.0.255.255 |
| ::FFFF:9 |
255.255.0.9 |
| ::FFFF:10 |
255.255.0.16 |
| ::FFFF:10A |
255.255.0.10 |
| ::FFFF:ABCD |
255.255.171.205 |
| ::FFFF:FFFF |
255.255.255.255 |
For information on IP address formats,
see IP address formats accepted by CICS.
- For both regions, inquire on the resource which relates
to the protocol that you are using (for example, URIMAP) and compare
to the listening TCPIPSERVICE resource. If you are using the IPIC
protocol, inquire on the both sets of complementary IPCONN and TCPIPSERVICE
resources to compare attributes. For example, inquire on the following
TCP/IP resource attributes:
- Inquire on the HOST option to determine the host name,
IPv4, or IPv6 address specified for the region. If you
have an IPv6 address or a hostname that resolves
to an IPv6 address in the HOST option, ensure that both CICS regions are operating in dual-mode environments.
- If there is a host name in the HOST option, this might
resolve to an IPv6 address at the domain name server. Trace points
SO 0436 and SO 0437 give details of resolved addresses, or consult
your system support representative to find out the IP addresses that
have been configured at the domain name server for this port.
- Look for any error messages or TCP/IP connection information
that might indicate the cause of the connectivity problem; for example,
a port sharing conflict or a problem because the task has not run
properly. You can inquire on socket application data (ApplData)
for each TCP socket owned by CICS to
correlate TCP/IP connections with the CICS regions
and transactions using them. ApplData is also available using Netstat
reports. For more information about CICS ApplData,
see TCP/IP management and control.
- Modify any resources that have not been correctly defined.
- Verify that traffic is flowing across the connection.
What to do next
The network connection is available. If the connection is
not available, contact your Network Administrator and request an investigation
into the network components that are being used to connect your CICS regions.