CICS® IA Version
5.1 provides sample jobs to migrate your CICS IA V3.1,
or CICS IA V3.2 DB2® tables to CICS IA V5.1
tables.
There are two methods to migrate the DB2 tables.
- Migrate all the old CICS IA DB2 tables to a new database.
- You must have created the new CICS IA V5.1
tables as described in Defining the database.
- CICS, DB2, WebSphere MQ, IMS™,
Natural, and Region tables.
- Load Module and CSECT Scanner tables.
- Affinity tables.
- Detailed CICS resource
tables.
- To migrate these tables from CICS IA V3.1
or CICS IA V3.2,
review and run:
- hlq.SCIUSAMP.DB2(CIUMIG31) for CICS IA 3.1
migration.
- hlq.SCIUSAMP.DB2(CIUMIG32) for CICS IA 3.2
migration.
- Migrate only the tables that have a different structure
from the tables in your previous CICS IA version.
This method is a single database migration method.
- Do not run any CICS IA 5.1
definition jobs for DB2 before
you use this migration method. This migration empties your CIU_CMDFLOW_DATA
table and does not use the CICS IA configurator
migration settings.
- Ensure that your old CICS IA DB2 settings remain unchanged.
- DB2 database for table spaces.
- DB2 schema name, (table qualifier).
- DB2 table owner.
- To migrate these tables from CICS IA V3.1
or CICS IA V3.2,
review and run:
- hlq.SCIUSAMP.DB2(CIUNMG31) for CICS IA 3.1
migration.
- hlq.SCIUSAMP.DB2(CIUNMG32) for CICS IA 3.2
migration.
Note: - CICS IA V5.1
does not provide jobs to migrate your existing collector VSAM files.
You must load all your VSAM data in to your existing DB2 tables before you proceed with the DB2 migration. CICS IA V5.1
does not provide migration of Command Flow data.
- The default tablespace size for tables created in DSN1TIAD step
of jobs CIUNMG3* might not suit your system requirements. If they
do not, change the size in the corresponding SQL files contained in
the hlq.SCIUSQL library.