Configuring an HA server region

How to configure an IPIC high availability (HA) server region.

Before you begin

The specific TCPIPSERVICE resource must be brought into service before the generic TCPIPSERVICE, so you must define them in the order set out in this procedure.

Restriction: IPIC HA makes use of function provided in CICS® TS V5.2 or later. Both client and cluster regions must be at this level. 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. IPIC HA connections must only be acquired by client regions. Attempts to acquire connections to an HA cluster can fail if there are other acquired IPIC connections between the client region and any regions within the cluster.

Procedure

  1. Define a specific TCPIPSERVICE resource to receive inbound requests on the local CICS region. This resource must listen on an address and port that is exclusively reserved for this region.
    1. Specify the IP address on which this CICS region will listen in the HOST attribute. The host name can be up to 116 characters in length, or can be an IPv4 or IPv6 address.
    2. Specify a port number on which the local CICS region listens for incoming client requests in the PORT attribute.
    3. Specify IPIC for the PROTOCOL attribute.
    4. Specify NO for the SOCKETCLOSE attribute.
    5. 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.
    6. Leave the SPECIFTCPS attribute blank.
    7. 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.
  2. Define a generic TCPIPSERVICE resource to receive inbound requests on the local CICS region. This resource must listen on an address and port that is shared by all the regions within the cluster.
    1. Specify the IP address on which this CICS region will listen in the HOST attribute. The host name can be up to 116 characters in length, or can be an IPv4 or IPv6 address.
    2. Specify a port number on which the local CICS region listens for incoming client requests in the PORT attribute.
    3. Specify IPIC for the PROTOCOL attribute.
    4. Specify NO for the SOCKETCLOSE attribute.
    5. 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.
    6. In addition set the SPECIFTCPS value to the name of the specific TCPIPSERVICE.
    7. You are advised to choose a name for the resource that alphabetically precedes that of the corresponding specific TCPIPSERVICE, if both resources are being installed from a single resource group. It will not be possible to open this resource unless the specific TCPIPSERVICE is also open.
  3. Optionally define one or more IPCONN resources for the client regions that may connect to the HA cluster. If you do not define these then the specific TCPIPSERVICE must be configured to support IPCONN autoinstall processing.
    1. Specify the IPCONN name. Specify a 4-character IPCONN name with four trailing spaces for CICS-to-CICS communications.
    2. Specify the host name in the HOST attribute, using the value that is specified in the TCPIPSERVICE resource in the remote CICS client 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.
    3. Specify in the PORT attribute the port number on which the remote CICS region will listen. This should be the same as the port specified in the TCPIPSERVICE resource in the client region.
    4. Specify the name of the specific TCPIPSERVICE resource on the local CICS region defined in step 1.
    5. Specify the application ID of the client region for the APPLID. If the client system is in a different network you must also specify the NETWORKID attribute.
    6. Specify NO for the HA attribute.
    7. Specify YES for the INSERVICE attribute to set if you want the connection to be available when the resource is created.
    8. Specify NO for the AUTOCONNECT attribute, to prevent an attempt being made to acquire a connection to the client region when this resource is installed: HA connections must only be acquired from client regions.
    9. Specify values for the RECEIVECOUNT and SENDCOUNT attributes to set how many receive and send sessions are allowed for the IPIC connection.

Results

When the resources are enabled on the local CICS regions, then that region will become part of the HA cluster and be able to process connection requests that client regions initiate.


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