Resource definition changes reported by CICS Configuration Manager
CICSĀ® Configuration Manager reports changes that it made to resource definitions in CSD files or contexts and that are recorded in its current journal.
The journal does not contain the following changes:
- Changes made outside CICS Configuration
Manager.
For example:
- Changes made using the CEDA transaction supplied with CICS.
- Changes made using the DFHCSDUP or BATCHREP utility to import
resource definitions from DFHCSDUP or BATCHREP export files. Note: CICS Configuration Manager writes to these export file formats but does not read them. To import from a DFHCSDUP export file, you use the DFHCSDUP utility; to import from a BATCHREP export file, you use the BATCHREP utility. The CICS Configuration Manager journal contains no record of these activities. If you want to report changes caused by importing an export file, use the CICS Configuration Manager export file format. For details on the different export file formats supported by CICS Configuration Manager, see Export and import with CICS Configuration Manager.
- Changes whose journal records have been unloaded from the current CICS Configuration Manager journal. For details, see Unloading and loading journal records.
- Changes to resource definitions in export files.
For example, if you use the CICS Configuration Manager ISPF dialog to copy a resource definition to an export file, the resource view of the report will not show that event. Copying a resource definition to an export file is not considered a change to a resource definition. Similarly, if you migrate a change package to an export file, neither the resource view nor the package view of the report will show changes to resource definitions in the export file.
If all of the target CICS configurations for a change package migration refer to export files, then the package view does not show the migrate event at all, not even in the summary report. If some target CICS configurations for a migration refer to export files, and others refer to CSD files or contexts, then the package view shows the migrate event, but its resource level only shows changes to resource definitions in CSD files or contexts.