Updating the Dependency database objects

CICS® IA provides a number of batch jobs to update the database from the VSAM files.

CIURESLD
Updates the CIU_RESOURCE table used by the CICS IA plug-in for CICS Explorer®.
CIUUPDB1
Updates the 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 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, DB2, MQ, Natural, and IMS), from all the dependency data files, CIUINT1 through CIUINT7.

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, on the other hand, you have separate sets of dependency data files for each region, you can run the jobs once 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.