CICS® IA provides a number of batch jobs to update the database from the VSAM files.
- CIUUPDB1
- Updates the CPSM and CICS table, CIU_CICS_DATA, from the CICS dependency data files, CIUINT1, CIUINT5, and CIUINT6.
- CIUUPDB2
- Updates the DB2® table, CIU_DB2_DATA, from the DB2 dependency data file, CIUINT2.
- CIUUPDB3
- Updates the WebSphere MQ table, CIU_MQ_DATA, from the MQ dependency data file, CIUINT3.
- CIUUPDB4
- Updates the IMS™ table, CIU_IMS_DATA, from the IMS dependency data file, CIUINT4.
- CIUUPDBN
- Updates the Natural table, CIU_NATURAL_DATA, from the Natural dependency data file, CIUINT7.
- CIUUPDB
Updates all tables, CICS,
and CICSPlex® SM, DB2, MQ, Natural, and IMS, from all the dependency data files, CIUINT1
through CIUINT7.Note:If you are not collecting DB2 data, you can remove step STEP060 through STEP091.
If you are not collecting MQ data, you can remove step STEP100 through STEP131.
If you are not collecting IMS data, you can remove step STEP140 through STEP171.
If you are not collecting Natural and Adabas data, you can remove step STEPN10 through STEPN41.
- CIURESLD
- Updates the CIU_RESOURCE table that is used by the CICS IA plug-in for CICS Explorer®.
If your dependency data files are shared by multiple CICS regions, you can use a single run of these jobs to store the dependency information for all the regions into the set of Dependency database objects.
If, however, you have separate sets of dependency data files for each region, you can run the jobs one time for each region in which you are interested and feed the dependency information for each region into the same set of Dependency database objects. For example, you must run multiple jobs, if you run the Collector on multiple regions, do not use a shared set of dependency files, and want to keep the dependency data for all the regions in the same set of Dependency database objects.
Run the Collector with your normal weekly workload to collect the base data and also run it at month ends, quarter ends, and year ends to collect data from infrequently run programs. When you have recorded all your applications, you might need to update the database only for new applications and changes.
CICS IA V3.2 introduced the ability to identify a CICS dependency collection at DB2 load time. This ability enables the user to load, manage, and compare resource usage by collection ID. Before you submit the job, you must review the collection name that you use. The job is first setup with a collection ID of _collid_. This collection ID is used in several places so you must run a global change to the collection ID of your choice. The collection ID can be up to 16 characters in length. If you want to change the collection ID every time you run the update jobs, you can edit the job, run "FIND COLLID=", and replace the collection ID name appropriately.
For more information about how to view and manage your data by collection ID, see Managing your CICS IA data.