Deployment analysis of resource definitions
Deployment analysis is the analysis of resource definitions that are installed in an active CICS® region, resource definitions that CICS would install when cold starting a region, and the differences between these sets of resource definitions.
Runtime, candidate, and CICS definitions
CICS Configuration Manager batch deployment analysis reports enable you to list or compare the following sets of resource definitions:
- Runtime resource definitions
- A set of installed resource definitions that CICS Configuration Manager collects from an active CICS region.
- Candidate resource definitions
- A set of resource definitions that CICS would
install when cold starting a CICS region. CICS Configuration
Manager collects candidate
resource definitions from the following sources:
CICS definitions
A set of resource definitions defined in a CSD file. A CICS definitions compare report compares the resources in two CSD files and shows the differences between those resources.
Types of deployment analysis report
You can produce deployment analysis reports to:
- List a set of runtime or candidate resource definitions
- Compare two sets in any combination:
- Two sets of runtime resource definitions
- Two sets of candidate resource definitions
- A set of runtime resource definitions with a set of candidate resource definitions
Two sets of CICS definitions
You can compare sets of resource definitions across any CICS releases supported by CICS Configuration Manager.
The following figure shows the different types of deployment analysis report, and the sets of resource definitions that they list or compare:



Listing or comparing these sets of resource definitions helps you to answer questions about your CICS environment, and avoid potentially costly surprises caused by unexpected differences.
The following table describes the different types of deployment analysis report:
Report type | What the report does | Questions that the report helps answer |
---|---|---|
Cold start compare | Compares a set of runtime resource definitions (installed in an active CICS region) with a set of candidate resource definitions (stored in a CSD file, a CICSPlex SM data repository, or a combination of the two). | What will be the effect of a cold start? This report helps you understand the difference that a cold start would make to the resource definitions installed in an active CICS region if you were to cold start that region using a particular set of candidate resource definitions. This report identifies anomalies where candidate resource definitions are new, missing, or differ from the runtime resource definitions. This report also identifies duplicate candidates, and candidates that rely on definitions that do not exist, or would not yet have been installed. For example, suppose that you have just created resource definitions that you have organized into a list in a CSD file. What would be the difference between cold starting a CICS region from the lists used previously, and cold starting the region with new lists? |
Candidates compare | Compares two sets of candidate resource definitions (stored in a CSD file, a CICSPlex SM data repository, or a combination of the two). | Are the candidates for two CICSPlex SM scopes, two CSD lists, or a
scope and a list the same? Will moving a group to a different position
in a list create problems? This report helps you understand how the resource definitions that CICS would install in a cold started region would differ depending on the set of stored resource definitions used. For example:
|
![]() ![]() |
![]() ![]() |
![]() This report is useful when you want to see only the differences between two CSD files without duplicate checks or referential integrity checks. ![]() |
Runtime resources compare | Compares two sets of runtime resource definitions (installed in two active CICS regions). | Are my cloned CICS regions
the same? This report helps you understand why two CICS regions, which you believe should have identical installed resource definitions, are exhibiting different behavior. For example, have CEMT SET or INSTALL commands introduced differences into your "cloned" regions? |
Runtime resources | Lists a set of runtime resource definitions (installed in an active CICS region). | What resource definitions are currently installed
in this CICS region? You can use this report to perform your own before/after analysis. For example, you can produce one report before cold starting a region, produce another after the cold start, and then run the comparison utility of your choice to analyze the differences between the two reports. |
Candidates | Lists a set of candidate resource definitions (stored in a CSD file, a CICSPlex SM data repository, or a combination of the two). | Which resource definitions would CICS would install in a cold
started region (based on the resource definitions stored in the
specified CSD file, context, or combination of the two)? In addition to listing candidate resource definitions, this report helps identify referential integrity ("consistency") issues between resource definitions, and issues caused by duplicate resource definitions. |
Check | Lists referential integrity issues in a set of candidate resource definitions (stored in a CSD file, a CICSPlex SM data repository, or a combination of the two). | Are these candidate resource definitions (stored
in the specified CSD file, context, or combination of the two) consistent
with one another? This report performs a superset of the consistency checks performed by the CICS CEDA CHECK command. While CEDA CHECK is limited to performing consistency checks on a CSD file, you can produce this CICS Configuration Manager deployment analysis check report for resource definitions that are stored in a CSD file, a CICSPlex SM data repository, or a combination of the two. The check report is identical to the candidates report, except that the check report contains checking results only, omitting the list of candidate resource definitions. You can also perform these checks via the ISPF dialog. For details, see Checking the consistency of lists and groups |
Cold start compare report
The deployment analysis report that compares a set of runtime resource definitions with a set of candidate resource definitions is known as a cold start compare report, because it helps answer the question: what will be the effect of cold starting a CICS region? Specifically, what is the difference between the set of resource definitions currently installed in an active CICS region, and the resource definitions that a CICS cold start would install from a CSD file (or CICSPlex SM data repository, or combination of the two)? Knowing the answer to this question helps you to systematically introduce required changes into your mission-critical CICS applications. Not knowing the answer risks introducing unexpected changes that can cause downtime.
The following figure illustrates the concept of a cold start compare report. You cold started a CICS region some time ago. Since then, the candidate resource definitions and runtime resource definitions might have been updated, introducing differences. What changes will the next cold start introduce?

Deployment analysis reporting process and components
The following figure shows how CICS Configuration Manager collects resource definitions for a deployment analysis report:



To collect runtime resource definitions you must have installed in the region either:
- 1
- The CICSPlex SM agent
- 2
- The CICS Configuration Manager agent (for details, see Optional: Configure the agent for CSD-based CICS regions)
You can use a filter file to suppress specific conditions or resource definitions from deployment analysis reports. For details on creating a filter file, see Filtering resource definitions from deployment analysis reports.
To read the filter file, the CICS Configuration Manager server uses a transient data queue named CCVX. The server dynamically defines CCVX (replacing any existing definition) using the data set name of the filter file specified by the FILTERDATASET parameter of the DEPLOY command in the SYSIN control statements for the job.
If you specify the optional ddname CCVFLTEX in your report JCL, the job output includes a filter file that contains a filter statement for each item in the generated report. To suppress an item from future reports, copy and paste the corresponding filter statement from this file to your own filter file.