When you have made all the changes that you want to a change package, you can then process the change package. The package must be made ready before the package can be processed, and the resources migrated.
When you have finished adding resource definitions to the change package, and finished editing those resource definitions, you can mark a change package as ready. Now you must also select a migration scheme for the change package.
If you chose to process the action now, the change package is processed and marked as ready. If you chose to create the JCL, then the change package is marked as ready when the JCL is submitted.
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 are different, it means that the candidates have changed, and CICS Configuration Manager does not allow the migration. This check protects you from migrating unexpected changes.
If a change package is marked as ready, but you want to postpone its approval or migration, you mark the change package as "unready". Later, when you want to approve or migrate the change package, you mark it as ready again. If any approver roles have approved the change package before it was marked as unready, then, when you mark the change package as ready again, these approvals are removed, even if none of the resource definitions in the change package have changed since it was first marked as ready.
If you chose to process the action now, the change package is processed and marked as unready. If you chose to create the JCL, then the change package is marked as ready when the JCL is submitted.
If a change package is marked as ready, you can process the package and migrate the resources.
If you chose to process the action now, the change package is processed and the resources are migrated. If you chose to create the JCL, then the resources are migrated when the JCL is submitted.
You can use the backout action to undo a migration.
If you chose to process the action now, the change package is processed and the migration is backed out. If you chose to create the JCL, then the migration is backed out when the JCL is submitted.