Ready processing and candidates

A change package can refer to resource definitions from many CICS® configurations. When you mark a change package as "ready", you select a migration scheme that identifies a set of source and target CICS configurations. Only the resource definitions from the source CICS configurations are candidates for migration. If a change package does not refer to any resource definitions from the source CICS configurations, then there are no candidates; there is nothing to migrate, and you cannot mark the change package as ready.

Figure 1. Which resource definitions are candidates for migration?
Begin figure description. The figure is described in the surrounding text. End figure description.

When you mark a change package as ready, CICS Configuration Manager calculates and stores checksums of the candidates. Later, when you migrate the change package, CICS Configuration Manager calculates new checksums and compares them with the stored values. If any of the checksums is different, it means that the candidates have been edited, and CICS Configuration Manager does not allow the migration. This protects you from migrating unexpected changes.

Specifically, if any of the following items has changed, then CICS Configuration Manager does not allow the migration:

Updates to the following items do not affect change package readiness:

CICS Configuration Manager calculates candidate checksums from a normalized resource definition record format, not the record format stored in the CSD file or the CICSPlex SM data repository. This normalized format is independent of:

By comparing resource definitions in a normalized format, and referring to CICS configuration names rather than the underlying CSD file or context, CICS Configuration Manager allows you to upgrade to a new CICS release, change the names of CSD files and contexts, or even move resource definitions between CSD files and CICSPlex SM data repositories, all without affecting change package readiness.