Change package approval
If both of the following conditions are met, then CICSĀ® Configuration Manager checks the approval status of change packages before migrating them:
- Approval checking is active for CICS Configuration Manager (ISPF dialog option 1.1 System Options).
- Approval checking is active for the migration scheme (option 1.3 Migration Schemes).
To check the approval status of a change package, CICS Configuration Manager requires the following:
- The change package must nominate an approval profile.
- The approval profile must contain an entry for the
migration scheme.
The entry for the migration scheme can specify from zero to five approver roles. Specifying no approver roles means that change packages using this migration scheme do not require approval. If you do specify approver roles, then any change packages that use the migration scheme must be fully approved before migration: all of the approver roles for the migration scheme must have approved the change package.
Tip: To migrate insignificant change
packages without approval, create an approval profile that contains
entries for migration schemes, but no approver roles. For example,
for documentation-only change packages, create an approval profile
called DOCONLY: insert entries for migration schemes, but do not define
any approver roles.
Figure 1. Does a change package require
approval?

If approval checking for a migration scheme is inactive:
- You can still assign approval profiles to change packages that use the migration scheme.
- CICS Configuration Manager rejects requests to approve or disapprove change packages with that migration scheme.
- If you activate approval checking later, any approval status that existed prior to deactivating approval checking remains.