Approve the change package
On the edit panel for the change package:
- Select the TOURDT migration scheme.
- Ready the change package. (If it is still ready from earlier in
the tour, then attempting to mark it as ready will have no effect.)
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.
- Try to migrate the change package: this should fail with the message "package not approved".
- Select the Approve command.
The approve processing panel appears.
- Select the Approve processing option with the approver role APPDEV.
- Select foreground execution.
- Press Enter.
The panel shows the message "Command successful", and the scheme status shows "Ready, partly approved":
Figure 1. Guided tour: Approving a change packageFile 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 4. Commands List the approve-candidate package commands 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.
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 would need to either:
- Undo the edit to the candidate, if you did not want it to be migrated. After undoing the edit, any existing approvals are preserved, and you can continue adding approvals, as before.
- Ready the change package again, if you wanted the edit to be migrated. This removes any existing approvals for the change package.
- Repeat the approval for the other two approver roles, QATEAM and
PROJMAN.
After approval by all three approver roles, the scheme status shows "Ready, fully approved".
You can now migrate the change package.