Migrate IIR for PTFs or From a Previous Version
Program Temporary Fixes (PTFs) RO93187 and RO93340 are now available for productgroup version 19. These PTFs require you to migrate IIR. You can migrate IIR from an existing version 19 installation, or you can migrate IIR in the course of upgrading from an earlier version of productgroup. If you are migrating from a version of productgroup that precedes 16.0 GA, you must verify the existing IIR installation. Otherwise, the migration process is the same for all versions of productgroup.
Program Temporary Fixes (PTFs) RO93187 and RO93340 are now available for
CA Database Management Solutions for IMS for z/OSversion 19. These PTFs require you to migrate IIR. You can migrate IIR from an existing version 19 installation, or you can migrate IIR in the course of upgrading from an earlier version of
CA Database Management Solutions for IMS for z/OS. If you are migrating from a version of
CA Database Management Solutions for IMS for z/OSthat precedes 16.0 GA, you must verify the existing IIR installation. Otherwise, the migration process is the same for all versions of
CA Database Management Solutions for IMS for z/OS.
We strongly recommend that you apply PTFs RO93187 and RO93340.
If you do not apply PTFs RO93187 and RO93340, migrate IIR in the following circumstances:
- You are upgradingCA Database Management Solutions for IMS for z/OSfrom version 16.0 or earlier.
- You are upgradingCA Database Management Solutions for IMS for z/OSfrom an incremental release of version 18.0 prior to the final Complete Access release. The IMS Information Repository (IIR) table schema was redesigned for the Version 18.0 Complete Access (INC00) release. If you were using IIR with an earlier increment and you want to continue using those schema, you can install the new IIR table schema while preserving the existing IIR tables in your system. After you follow this procedure, you can still use the reporting IIR jobs from previous versions.
Use this scenario to guide you through the process:
- If you are migrating from Version 16.0 or lower, verify the existing IIR installation.
- If you have applied PTFs RO93187 and RO93340, follow the migration procedure for those PTFs.
The following diagram illustrates this scenario:
Back Up the CA Datacom/AD Environment
During the CA Datacom/AD installation, you are instructed to run the AD
nnBKUP job. This job creates a backup of the CA Datacom/AD environment, which includes everything except the data that is stored in the IIR database.
To back up the CA Datacom/AD environment, reexecute AD
nnBKUP. The IIR table definitions are saved with the CA Datacom/AD environment information.
We recommend standardizing this job for your environment and adding it to the regularly scheduled system backups. These backups are only needed in the case of a system failure or accidental deletion of a CA Datacom/AD system data sets. If this occurs, contact
Broadcom Supportfor assistance in restoring the required data sets.
Start the CA Datacom/AD Environment
Executing the IIR installation or migrating jobs requires that the CA Datacom/AD environment be up and operational. This environment must be available for any access to the CA Datacom/AD databases.
To start the CA Datacom/AD environment, execute the AD
nnSTRT job in the CA Datacom sample library;
nnindicates the release number. For example, submit AD12STRT to start CA Datacom/AD r12.
This job is a long running task. We recommend submitting this job to a job class without a time or CPU limit.
Common use and maintenance of IIR does not require that you ever stop the CA Datacom/AD environment. For information about how to stop the CA Datacom/AD environment, see the
CA Datacom documentation.
Verify Existing IIR Installation
Migration from Version 16.0 or lower.
New tables have been added to enhance the capabilities of IIR. If you have an older version or IIR, these new tables might be missing in your installation. Before you migrate to new IIR tables, verify that your current IIR installation contains all tables.
Follow these steps:
- Run the IIRCXX job that is provided in thehlq.CIMTSAMP library.
- Review the job output. Search for the following table names (strings): DBA00A, DBA00B, DBA00C, DBA00D, DSA001.
- If a tablename is not found, locate and edit the table member in thehlq.CIMTSAMP library. Save your changes and submit the edited member for execution. The expected return code is 0.For DBA00A, use the tablename IIRADD0A.For DBA00B and DBA00C, use the tablename IIRADDBC.For DBA00D, use the tablename IIRADD0D.For DSA001, use the tablename IIRADDSA.
Migrate or Upgrade the Tables
You have applied PTFs RO93187 and RO93340...
Migrate the Tables to Support PTFs
After you verify that your IIR installation contains all tables (see the paragraph Verify the Existing IIR Installation), you can follow this simplified migration process. Generally the process consists of four steps you are required to perform:
- Back up the existing data and reformat it for later use.
- Drop the existing database schema and underlying data.
- Redefine the IIR schema with the new changes.
- Reload the data created from step #1.
Ensure that the CA Datacom Multi-User Facility (MUF) is up and running on the same LPAR where you submit the job. If successful, all steps and the job end with return code zero (RC=0). All the steps must be run in the defined order.
Follow these steps:
- Back up existing data for the migration. (This step is not a replacement for the paragraph "Back up the CA Datacom/AD environment." We strongly recommend that you follow both backup processes.) Customize and submit the IIRMIG1 sample job. This job creates several backup data sets: the IIRDB615.BACKUP data set contains most of the data from database, and the DBA002 BACKUP data set contains the specific reformatted DBA002 table.Warning!This job (by default) blocks access to the IIR database. Other users (including CA IMS Tools) do not have access to the IIR database during the rest of the migration. Blocking access is necessary for migration. If you are only testing the backup job, add STARTDB as the final step of the job. This step reopens the database to users.
- Clear the existing IIR table definitions. Customize and submit an IIRDEPR sample job. Besides cleaning the Datacom/AD Data Dictionary and Catalog, this job also deletes IIR database data sets for areas IXX615, IIR615, DBA615, DBO615, SIB615, DBC615, and HPR615. In the next step, these data sets are newly allocated and reinitialized. We recommend that you record the allocation parameters and sizes of those data sets for use in the next step.
- Edit and submit thehlq.CIMTSAMP members IIRINS1, IIRINS2, and IIRINS3, in that order.
- Reload the old data into the new tables. Customize and submit the IIRMIG2 sample job. When the job is complete, the IIR database schema is updated, including existing data. You can start using the database. The IIRMIG2 job first reloads the large IIRDB615.BACKUP data set. Other steps reload particular tables, such as DBA002.
You have not applied PTFs RO93187 and RO93340...
Migrate IIR Database and Tables from Version 16.0 or lower.
After verifying that your IIR installation contains all tables, migrate the new IIR database and tables. A batch utility program to migrate the IIR database and tables is provided in the sample library (
Follow these steps:
- Edit the IIRMIG1 member in thehlq.CIMTSAMP library and save your changes.
- Submit the edited member IIRMIG1 for execution. Expected return code is 0.
- Set the IIRHIST option in the ITKOPTN0 member in the sample library (hlq.CIMTSAMP) to Yes. Link the member using the JCLOPTNA job.
The IIR database and tables are ready for use. We recommend backing up the CA Datacom/AD environment before you start collecting data into IIR tables.
Update IIR Database and Tables
from Version 18.0 (INC00).
After the Incremental Release of IIR Version 18.0, new tables were added to the IIR database. A batch utility program to add these tables is provided in the sample library (
Follow these steps:
- Edit the IIRUPD1 member in thehlq.CIMTSAMP library and save your changes.
- Submit the edited member for execution. Expected return code is 0.
(Optional) Set Up the IIR Historical Reporting Application or Conditional Reorganization
This step is optional. Perform this step if you want to view IIR historical data or set up Conditional Reorganization thresholds.
The IIR Historical Reporting application reads data from the IIR database and provides DBD job reports through the ISPF interface. Conditional Reorganization allows you to base reorganization on user-defined thresholds. These thresholds are compared with the latest statistics collected from CA Database Analyzer for IMS. If the thresholds are exceeded, the relevant database is reorganized.
Both applications use the plan file, which provides a description of the SQL query that particular load modules execute on the CA Datacom/AD database. To enable the SQL access for applications, import the plan definition to CA Datacom/AD.
Follow these steps:
- Ensure that the CA Datacom Multi-User Facility (MUF) is up and running on the same LPAR where you submit the job.
- Edit the IIRPLNIN member of the sample library (hlq.CIMTSAMP) to mirror the IIR configuration from the $ITK member of the CLIST.
- Specify the plan to import in the TRANSF ddname.The plans for supported CA Datacom/AD releases are provided in the sample library members IIRPLNnn, wherennindicates the release number. The plan for the most recent release is imported by default.
- Run IIRPLNIN.The plan file is imported to CA Datacom/AD.
To export a plan, execute the IIRPLNEX job that is provided in the sample library.