Creating the upgraded Db2® environment

This section describes the steps that are required to define your CICS® IA Db2® database and how to review and submit the sample jobs that you configured in the previous section.

When the configuration utility runs to update your Db2® environment variables, you should have the following output data sets.
  • hlq.SCIUSAMP.Db2
  • hlq.SCIUSQL.Db2
  • hlq.SCIUDAT1.Db2
  • hlq.SCIUDAT2.Db2
The data set hlq.SCIUSAMP.Db2 contains the sample jobs that are required to define, upgrade, and maintain your CICS® IA Db2® environment.

If you chose to use the first upgrade method Copy the previous CICS IA Db2 tables to a new database, perform the tasks that are described in Step - 1A Creating and updating the IA Db2 database, and then proceed to Step 1C - Updating the stored procedures.

If you chose to use the second upgrade method,Upgrade the previous CICS IA Db2 database to the new structure, perform the tasks that are described in Step 1B - Updating the IA Db2 database and then proceed to Step 1C - Updating the stored procedures.

Step - 1A Creating and updating the IA Db2® database

To create the CICS® IA database, perform the following steps:
  • Review sample job CIUDBCQ in hlq.SCIUSAMP.Db2.
  • Review the associated SQL member, CIUMAIN, in hlq.SCIUSQL.Db2.
  • Run sample job CIUDBCQ to create the database objects. This job completes with a return code of 0.

To copy the data from your previous CICS® IA database, perform the following steps:

If you are upgrading from CICS® IA 5.3:
  • Review and run sample job CIUMIG53 to copy the data. This job completes with a return code of 0.
If you are upgrading from CICS® IA 5.5:
  • Review and run sample job CIUMIG55 to copy the data. This job completes with a return code of 0.
If you have applied maintenance to CICS® IA 6.1 that alters the CICS® IA 6.1 database schema, select 55 as your CICS IA migration version:
  • Review and run sample job CIUMIG55 to copy the data. This job completes with a return code of 0

Step 1B - Updating the IA Db2® database

To update your existing CICS® IA database, perform the following steps:

If you are upgrading from CICS® IA 5.3:
  • Review and run sample job CIUNMG53 to update the database structure. This job completes with a return code of 0.
If you are upgrading from CICS® IA 5.5:
  • Review and run sample job CIUNMG55 to update the database structure. This job completes with a return code of 0.
If you have applied maintenance to CICS® IA 6.1 that alters the CICS® IA 6.1 database schema, select 55 as your CICS IA migration version:
  • Review and run sample job CIUNMG55 to update the database structure. This job completes with a return code of 0.

Step 1C - Updating the stored procedures

If you are updating the database on Db2® 9 or later, follow these steps:
  • Review the sample job CIUDBCP1 in hlq.SCIUSAMP.Db2.
  • Review the associated SQL member, CIUSPDL1, in hlq.SCIUSQL.Db2 and remove the comments to DROP the Stored Procedures.
  • Run sample job CIUDBCP1 to create the database objects. This job completes with return code 0.
If you are updating the database on Db2® 8 or earlier, follow these steps:
  • Review the sample job CIUDBCP2 in hlq.SCIUSAMP.Db2.
  • Review the associated SQL member, CIUSPDL2, in hlq.SCIUSQL.Db2 and remove the comments to DROP the Stored Procedures.
  • Run sample job CIUDBCP2 to create the database objects. This job completes with return code 0.

Step 2 - Rebind the IA Db2® packages

To bind the Db2® batch packages that are required by the CICS® IA database, follow these steps:
  • Review the sample job CIUDBNB in hlq.SCIUSAMP.Db2.
  • Review the associated SQL member, CIUGRNTB, in hlq.SCIUSQL.Db2. This sample member includes sample SQL to grant a RACF® group or user ID access to the CICS® IA plans. It is used in the STEP 3 of the sample job.
  • Run the sample job CIUDBNB to bind the Db2® batch programs that are used by CICS® IA sample jobs and to grant access to the bound plan. This job completes with a return code 0.

Step 3 - Loading static Db2® tables

CICS® IA uses the following static tables:
CIU_VERSION
The CIU_VERSION table contains the CICS® IA Version and Service information and is used by the CICS® IA plug-in for CICS Explorer®.
  • To load the version table, review and run job hlq.SCIUSAMP.Db2(CIUVERLD). This job completes with a return code 0.
CIU_TRANSLATORS
The CIU_TRANSLATORS table contains a one to one relationship between the IBM® program component numbers for compilers, translators, and linkage editors and a description for each component.
  • To load the translator table, review and run job hlq.SCIUSAMP.Db2(CIUTLOAD). This job completes with a return code 0.
CIU_THREADSAFE_CMD
The CIU_THREADSAFE_CMD table contains information on whether an EXEC CICS® command is threadsafe or not for each version of CICS® TS. It is used by the threadsafe report program and the stored procedure to determine whether a command is threadsafe.
  • To load the threadsafe table, review and run job hlq.SCIUSAMP.Db2(CIUTSLOD). This job completes with a return code 0.
CIU_TRUEEXIT_INFO
The CIU_TRUEEXIT_INFO table contains a one to one relationship between the CICS® TRUEs that are used in your environment and a description for each TRUE. This table is used by the CICS® IA plug-in for CICS Explorer®.
  • To add your own TRUEs to the table, edit and save hlq.SCIUDAT2.Db2(CIUTRCD).
  • To load the TRUE exit table, review and run job hlq.SCIUSAMP.Db2(CIUTRLOD). This job completes with a return code 0.

Step 4 - Loading the CIU_CICS_CHAINP table (for Db2® 9 onwards)

To load the CIU_CICS_CHAINP table, compete the following steps:
  • Review the sample job CIUCHPFL in hlq.SCIUSAMP.Db2.
  • Run the sample job CIUCHPFL. This job completes with a return code 0.

Step 5 - Db2® Stored Procedures Setup

CICS® IA uses Db2® Stored Procedures to perform complex Db2® tasks.

If you are running Db2® 910 or later, CICS® IA uses Native Db2® stored procedures and these stored procedures are defined in STEP 1C.

If you are running Db2® 810 or earlier, CICS® IA uses external stored procedures and these stored procedures are defined in STEP 1C.

External Db2® stored procedures run in a started task that is called WLM (Workload Manager) associated with each Db2® subsystem. Sample JCL for a WLM started task is in hlq.SCIUSAMP.Db2(CIUSPTSK). If you already have a Db2® WLM task, you need to update to change the CICS® IA load library hlq.SCIULOAD in the STEPLIB concatenation in this JCL to the latest release.
Note:
The name of the started task must match the one that is supplied in the CICS® IA configuration variable Db2® WLM PROCEDURE NAME.

You can find more information about implementing Db2® Stored Procedures in the Db2® for z/OS® Administration Guide.