On the edit panel for the change package:
Notice that the ready panel for the change package reports the "scheme status" as "…, no approvals applied". The "scheme status" is the status of the change package for this migration scheme.
Before applying approvals, let us attempt to migrate the change package without approval.
The approve processing panel appears.
The panel shows the message "Command successful", and the scheme status shows "Ready, partly approved":
File Menu Settings Help ────────────────────────────────────────────────────────────────────────────── Approve Change Package TOURPKG Command successful Command ===> Name . . . . . : TOURPKG Description . . : Guided Tour Change Package Scheme name . . : TOURDT Scheme status . : Ready, partly approved Choose a processing option and press Enter 1 1. Approve Approve the change package for role . . . . APPDEV + 2. Disapprove Disapprove the change package for role . . . + 3. List List the approve-candidate CICS resources Execution mode Enter "/" to select option 1 1. Foreground Edit JCL before user submit 2. Batch Summary of approvers Approver role: PROJMAN QATEAM APPDEV Approved by: <required> <required> CICSUSER
Notice that the summary at the bottom of the panel shows your user ID under APPDEV.
What happens if a candidate is edited?
Suppose that someone now edited one of the candidate resource definitions in the change package. Subsequent attempts to approve this change package would fail, because CICS® Configuration Manager detects that the candidate has changed. You need to either:
or
After approval by all three approver roles, the scheme status shows "Ready, fully approved".
You can now migrate the change package.