Configuring a CICS Region

Configuring a CICS region is a process that requires you to work closely with your system administrator and establish the actual connection. First, you and your administrator define the CRM's logical unit to the CICS region with a CICS Connection Definition. Then you must define the connection characteristics of the CRM's connection to the CICS region with a CICS Session Definition. Then you must gather this connection information and use it as input for the CICS adapter CRM gateway connection.

Parameters and Steps for Connecting to a CICS Region

A system administrator will most likely configure the CICS region and establish the CICS connections to the CRM. This section provides information to help the administrator establish those connections.

For every CICS region that the CRM connects to, resource definitions for the CRM's logical unit must be configured in the CICS region. This configuration consists of CICS connection and session resource definitions. These CICS resource definitions must be installed in each CICS region to which the CRM connects.

To establish CICS region connectivity you must:

Create a logical unit for the CICS region.
Add APPC to the CICS region.
Define the CICS connection definition.
Define the CICS session definition.
Install the CICS connection and session definitions.
Verify connection and session status.

Top of page

Step 1: Create a Logical Unit for the CICS Region

The CICS application program major node is also the CICS logical unit. This application program major node is defined to VTAM when the CICS region is created. Ask your system administrator to provide the CICS VTAM APPLID of the created CICS region.

Top of page

Step 2: Add APPC to the CICS Region

To enable the CICS region for APPC, start the region with the following system initialization parameter:

ISC=YES

This enables inter-system communication.

Top of page

Step 3: Define the CICS Connection Definition

In each CICS region to which the CRM connects, a system administrator must define and install a connection resource definition and session resource definition in the region. The connection and session definitions should be defined in the same resource group. This group of definitions defines the CRM as a partner Logical Unit to the CICS region, and associates connection characteristics to the link between the CRM and CICS.

The following parameters represent the minimum requirements for defining the CICS connection.

ACCESSMETHOD(VTAM): Indicates this resource is accessed via VTAM.
PROTOCOL(APPC): Indicates that this connection is used for APPC.
NETNAME(xxx): The name of the CRM's logical unit created in VTAM.
ATTACHSEC(xxx): The security protocol used for this connection. Set to LOCAL, IDENTIFY, or VERIFY. If security credentials are not passed between WebLogic Server and CICS, set this to LOCAL. If user IDs are required between WebLogic Server and CICS set this parameter to IDENTIFY. If user IDs and passwords are required, set this parameter to VERIFY.
AUTOCONNECT(NO): Sessions for this connection should not be automatically initialized when CICS is started. The CRM will initiate session acquisition.

The following syntax shows an example CICS connection definition:

DEFINE CONNECTION(IWY1)
       GROUP(IWAY)
       DESCRIPTION(LOGICAL UNIT FOR CRM1 TO ACCESS THIS CICS)
       ACCESSMETHOD(VTAM)
       PROTOCOL(APPC)
       NETNAME(IWYAPPL1)
       ATTACHSEC(LOCAL)
       AUTOCONNECT(NO)

Top of page

Step 4: Define the CICS Session Definition

In each CICS region that the CRM connects to, a session resource definition must also be defined and installed in the region. The following parameters represent the minimum requirements for defining the CICS session:

CONNECTION (xxx): Should be set to the CICS connection definition for CRM's logical unit.
AUTOCONNECT (YES): Determines how the activation of the session is negotiated. YES enables the CICS/ESA host to negotiate its own winner sessions once the CRM starts the initiation of session acquisition.
MODENAME(xxx): This is the VTAM LOGMODE name used for these sessions.
MAXIMUM(SESSNBR, WINNER): Defines the total number of sessions for this connection, and the number that are established by the CICS region. The SESSNBR number defines the total number of sessions allowed for this connection. The WINNER number defines the sessions that are established by the CICS region. It is recommended that you set the WINNER numbers to be the remainder of the MAXIMUM SESSIONS after you define the number of WINNER numbers needed by the CRM.

The following syntax shows an example CICS connection definition:

DEFINE SESSION(IWY1)
       GROUP(IWAY)
       CONNECTION(IWY1)
       DESCRIPTION(SESSIONS FOR CRM1 TO ACCESS THIS CICS)
       PROTOCOL(APPC)
       AUTOCONNECT(YES)
       MODENAME(SMSNA100)
       MAXIMUM(20,10)

Top of page

Step 5: Install the CICS Connection and Session Definitions

To install the resource definitions, put them on the host in a separate group. You may use the CEDA INSTALL command to install the group to CICS.

For example:

CEDA INSTALL GROUP(IWAY)

Note: The CRM cannot connect to the CICS region until the resource definitions are installed and ready for service by CICS.

Top of page

Step 6: Verify Connection and Session Status

After you have installed the resource definitions, you can verify the status of connections and sessions using the CICS/ESA system commands shown in the following syntax.

CEMT I CONN(IWY1) **View the status of the connection
CEMT I NET(IWYAPPL1)     **View the status of the sessions
CEMT I MODENAME(SMSNA100)   **View the status of the mode