2 Changing CICS installation parameters

If you plan to run OAM under CICS, make the following changes to your CICS installation before using OAM:

2a Update or create CICS PLT.

You must perform this step at initial installation. For migration, you must verify or perform this step if you determine that it has not yet been completed in your current environment.

If you have a program list table (PLT) to specify programs to be executed in the post-initialization phase of CICS startup, add the following entry:
```
DFHPLT TYPE=ENTRY,PROGRAM=CBRICONN
```
This entry names the OSR CICS initialization load module (CBRICONN) and invokes CBRICONN when CICS is initialized.
If you do not have a PLT to specify programs for execution in the post-initialization phase of CICS startup, use one of the following to generate your CICS PLT:
```
 
DFHPLT TYPE=INITIAL,SUFFIX=xx
DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM
DFHPLT TYPE=ENTRY,PROGRAM=CBRICONN
DFHPLT TYPE=FINAL
END
```
Related reading: For additional information on DFHPLT, see the IBM Knowledge Center for CICS Transaction Server for z/OS.

2b Update CICS CSD.

You must perform this step at initial installation. For migration, you must verify or perform this step if you determine that it has not yet been completed in your current environment.

If you are a new CICS Transaction Server (CICS TS) user, you must create and initialize a CICS System Definition (CSD) file. Define the OAM module CBRICONN and add the group to your CICS region group list.

DEFINE PROGRAM(CBRICONN) GROUP(xxx) LANGUAGE(ASSEMBLER) CEDF(NO)ADD GROUP(xxx) LIST(yyy)

For xxx, substitute the group name for your CSD OAM definitions (that is, OAM).For yyy, substitute the CICS region name for your OAM enabled CICS region (that is, CICSA).

Attention: CICS TS does not support macro definitions for the Processing Program Table (PPT) resource. If you are moving to CICS TS from an earlier release and you have macro level resource definitions for the PPT, you must migrate the resources to the CSD. For information on how to do this, see the topic "Getting started with resource definition" in CICS Transaction Server for z/OS in the IBM Knowledge Center.

Related Reading: For more information on the CICS System Definition (CSD) file, see the IBM Knowledge Center.

2c Update CICS SIT.

You must perform this step at initial installation. For migration, you must verify or perform this step if you determine that it has not yet been completed in your current environment.

Add the following entry to the CICS system initialization table (SIT) to supply initialization parameters to CICS:

        PLTPI=vv,       *** POSTINITIALIZATION CONNECTION

where:

vv: Specifies the suffix of the DFHPLT module

2d Connect DB2 to CICS.

You must perform this step at initial installation. For migration, you must verify or perform this step if you determine that it has not yet been completed in your current environment.

CICS TS provides Resource Definition Online (RDO) support for DB2 resources. Define the following objects using RDO.

DB2CONN to connect DB2 to CICS. 
DB2ENTRY for plan CBRIDBS.

These objects describe the global attributes of the CICS DB2 connection and the relationship between CICS transactions and DB2 resources (including application plans and command processors). For information on how to create these objects using Resource Definition Online (RDO), see the CICS Transaction Server for z/OS in the IBM Knowledge Center.

Attention: CICS TS Version 1 Release 3 and above do not support the use of DSNCRCT macro definitions to create the Resource Control Table (RCT). If you are moving to CICS TS, use CICS RDO to support DB2 resources instead of using DSNCRCT macros.

2e Copy CBRICONN to DFHRPL.

You must perform this step at initial installation. For migration, you must verify or perform this step if you determine that it has not yet been completed in your current environment.

CBRICONN must be contained in a load library in the DFHRPL concatenation. CBRICONN is delivered in SYS1.LINKLIB. You might add SYS1.LINKLIB to your DFHRPL concatenation or copy CBRICONN into another load library in the concatenation. If you choose not to use SYS1.LINKLIB in your DFHRPL list, you must remember to upgrade the copy of CBRICONN every time the module in SYS1.LINKLIB is changed due to maintenance or a new release of OAM.