To define an IPIC connection, you create two resources, IPCONN and TCPIPSERVICE, on each CICS® region that you want to connect. You can either create new IPIC connections, or you can migrate your existing APPC connections.
Before you begin
Restriction: IPIC supports specific intercommunication
functions and releases. See the related links for this topic for more
information.
TCP/IP services must be active in the CICS regions. You can activate
TCP/IP services by setting the TCPIP system initialization
parameter to YES.
Procedure
- Define a TCPIPSERVICE resource
to receive inbound requests on the local CICS region.
The name of the TCPIPSERVICE
resource must match the value of the TCPIPSERVICE attribute for the
IPCONN resource.
- Specify the IP address on which this CICS region will
listen in the HOST attribute. The ANY option specifies that CICS listens
on any of the addresses known to TCP/IP for the host system.
The
host name can be up to 116 characters in length, or can be an IPv4
or IPv6 address. If you use an IPv6 address, ensure that you are operating
in a dual-mode environment and that the client or server that you
are communicating with is also operating in a dual-mode environment.
- Specify a port number on which the local CICS region listens for incoming client requests
in the PORT attribute.
- Specify IPIC for the PROTOCOL
attribute.
- Specify NO for the SOCKETCLOSE
attribute.
- Specify the 4-character ID of the CICS transaction that runs the DFHISCOP program
as the value of the TRANSACTION attribute.
The default
transaction for IPIC is CISS.
- Leave the SPECIFTCPS attribute blank.
- Optional: Specify the name of the IPCONN
autoinstall user program as the value of the URM attribute.
If
you do not specify this attribute, CICS uses
the CICS-supplied default IPCONN autoinstall user program, DFHISAIP.
Specify NO to disable autoinstall.
- Create an IPCONN resource
on the local CICS region.
- Specify the IPCONN name. Specify a 4-character IPCONN
name with four trailing spaces for CICS-to-CICS communications.
- Specify the host name in the HOST attribute, using the
value that is specified in the TCPIPSERVICE resource in the remote CICS region.
For
example, hostb.example.com
The host
name can be up to 116 characters in length, or can be an IPv4 or IPv6
address. If you specify an IPv6 address (or a host name that resolves
to an IPv6 address), ensure that you are operating in a dual-mode
(IPv4 and IPv6) environment and that the client or server that you
are communicating with is also operating in a dual-mode (IPv4 and
IPv6) environment.
- Specify in the PORT attribute the port number on which
the remote CICS region will
listen.
Specify NO if this IPCONN
resource is not used for outbound requests and you are using the CICS Transaction Gateway.
- Specify the name of the TCPIPSERVICE resource on the
local CICS region that specifies
the inbound attributes of the IPIC connection as the value for the
TCPIPSERVICE attribute.
- Specify values for the APPLID and NETWORKID attributes
if you want to connect to a remote system that is in a different network.
The combination of APPLID and NETWORKID attributes ensures that
the remote CICS region is referred
to by a unique name.
- Optional: Specify YES or NO for
the INSERVICE attribute to set if you want the connection to be available
when the resource is created.
- Specify values for the RECEIVECOUNT and SENDCOUNT attributes
to set how many receive and send sessions are allowed for the IPIC
connection.
- Create a TCPIPSERVICE resource in the remote CICS region.
- Create an IPCONN resource in the remote CICS region.
Specify AUTOCONNECT(YES)
to establish the connection between the two CICS regions.
Results
When the resources are enabled on the local and remote CICS regions, the connection is
established between the CICS regions.
What to do next
You can use the IBM® CICS Explorer® or
Web User Interface to view and update your IPIC connections. If you
do not specify AUTOCONNECT(YES) for one of the IPCONN
resources, you must acquire the connection by updating the status
of the resource.