Administration
In keeping with the ChangeMan ZMF methodology of flexibility in rule enforcement, the decision as to the degree of INFO Option participation is left up to the Global and Local Administrators.
Global Administration
The Global Info/Management Rule panel contains the information management change rule.
To access the Global Info/Management Rule panel, take the following steps:
-
Select A (Admin) from the Primary Option Menu. Press Enter.
-
Select G (Global) from the Administration Options panel. Press Enter.
-
From the Global Administration Options panel, select O (Option) and press Enter. The Global Selectable Options panel (CMNGBSOP) appears.
CMNGBSOP GLOBAL Selectable Options Option ===> 2 Db2 Maintain Db2 information 3 INFO Specify Info/Management change rule 4 OFM Configure Online Forms Manager 5 IMS Control Region IDs and Library Sub-Type information -
From the Global Selectable Options panel, if you have the privilege to access the global INFO/Management Change Rule, type 3 and press Enter.
You can set the global INFO/Management Change Rule to 0 (the most liberal value) if your company desires to give individual application administrators complete latitude in choosing INFO/Management Change rules.
CMNGOINF GLOBAL Info/Management Rule
Command ===> _________________________________________________________________
Info/Management change rule . . . 0 (0-5)
Enter "/" to select option
_ Info VSAM file interface
_ Info System Bus interface
/ Info Change System
Info System Bus Soap Member . . .
The rules and their meanings are summarized below:
| Rule | Explanation |
|---|---|
| 0 | INFO Option has no bearing and no communication is necessary. |
| 1 | INFO Option has some bearing in that it is kept apprised of packages being created. If the INFO subtask is temporarily detached, the transfer of information is excused. Keeping INFO Option in synchrony is not critical. The user specified in the Notify user field is apprised of any failure to transfer data to INFO Option. |
| 2 | Rule 1, plus the fact that updates, including status changes, to change packages are also reflected in INFO Option change records. |
| 3 | Rule 2, plus there is no excuse for the INFO Option subtask to be detached. Every change package is tied to INFO Option. The potential for approving packages from INFO Option under the entity INFOMGMT starts with this rule. Approving Through the INFO Option |
| 4 | Rule 3, plus INFO Option has even more bearing in that every planned change package must already have a companion INFO Option change record created in advance. At change package creation time, the work request number must refer to an existing INFO Option change record that has not already been chained to another package. Data elements from the change record are used as suggestions for creation of the change package. Unplanned packages may usurp pre-authorization of INFO Option. |
| 5 | Rule 4, plus even unplanned packages fall into this category. |
Approving Through the INFO Option
With Rules 3 through 5, it is possible for INFO Option to be charged with approval responsibility. Any given (simple) package contains a list of entities for gathering approvals. If the entity INFOMGMT is on the approval list at freeze time, INFO Option is charged with approval or rejection responsibility for that entity. INFOMGMT cannot be the last chronological entity on the approval list and the concept of hierarchical approval gathering does not apply when INFOMGMT is an approving entity.
Only the Global Administrator may intercede on behalf of INFOMGMT. The points in time that ChangeMan ZMF interrogates INFO Option for approval under that entity are
-
Package Freeze time.
-
Every opportunity that the package is presented for approval by any potential approver or rejecter, and it has not already been approved or rejected by INFO Option.
Local Administration
Since the importance of INFO Option may vary from application to application, each application (project) mnemonic has the option of setting the INFO/Management Change Rule level. It is recommended that the Local INFO/Management Change Rule be set to 1 in the beginning. Option A.A.O of the Application Administration panel lists all the selectable options that have been purchased for your data center. Since the panel is dynamically built, only the selectable options that have been purchased are shown on this panel and it may differ substantially from the panel you observe. If you are a Local Administrator, you have the privilege to access the INFO/Management Change Rule. To do so, type 3 and press Enter.
CMNAPSOP ACTP - Selectable Options
Command ===> _________________________________________________________________
2 Db2 Maintain Db2 information
3 INFO Specify Info/Management change rule
5 IMS Control Region IDs and Library Sub-Type information
The global INFO/Management Change rule can be set to 0 (the most liberal value) if your company desires that Local Administrators have complete latitude in choosing INFO/ Management Change rules by application.
CMNLOINF ACTP - Info/Management Rule
Command ===> _________________________________________________________________
Info/Management change rule . . . 0
The requirement for a Work Request Number affects the INFO/Management Change rule setting. If the local administrator selected:
Require Work request
and
Info/Management change rule . . . 1
then the user (package creator) could not leave the Work Request Number blank and bypass the panel syntax checking. He would be forced to type an INFO Option change record number, and there may not be one at this point in time.
-
If the INFO/Management Change rule is 4 or 5, requiring a Work Request Number is appropriate.
-
If the INFO/Management Change rule is 1 to 3, requiring a Work Request Number is probably not appropriate.
-
If the INFO/Management Change rule is 0, requiring a Work Request Number, is a decision independent of INFO Option.
The global Work Request Number parameter is found on the Global Parameters panel (CMNGGP03) (option A.G.1), shown below with the pertinent line in blue:
CMNGGP03 Global Parameters - Part 3 of 8
Command ===> _________________________________________________________________
Enter "/" to select option
Baselines
/ Stacked Reverse Delta
_ Panvalet
_ User defined
_ Librarian
_ Librarian Access Method (LAM)
_ Notification Vehicles
/ Email
/ Batch
Other options
_ Require Work request
_ Require Department
_ Disable installation calendar
/ Allow temporary packages
_ Process participating packages by install date
_ Hierarchical approval process
/ Use global notification file
/ Allow application update to file
_ Force display of global notification file
Global notification file . . CMNTP.S7.NOTIFY
...
The application’s Work Request Number parameter is found on the application Parameters (CMNGLP03) panel (option A.A.1):
CMNGLP04 ACTP Parameters - Part 4 of 4
Command ===> _________________________________________________________________
Aging - installed packages . . . . . 0 (0 to 9999 days)
- staging datasets . . . . . . 0 (0 to 9999 days)
- component history . . . . . 0 (0 to 9999 days)
- staging versions . . . . . . 0 (0 to 9999 days)
Management class . . . . . . . . . . ________
Storage class . . . . . . . . . . . ________
Default unit name . . . . . . . . . SYSDA (Generic disk unit)
Default volume serial . . . . . . . ________
Job statement information:
//CMNSTART JOB , 'ACCOUNT INFO',
// CLASS=A,MSGCLASS=X
//* JOBCARD
//*
Enter "/" to select option
_ Require Work request
_ Require Department
_ Hierarchical approval process
/ Eliminate save to personal library
/ Edit staging recovery mode on
_ Build install JCL at approve
/ Use like-lod in syslib
_ Use package syslib service
...
Scenarios
The setting of INFO/Management Change rules may vary from application to application. The impact of each setting can be illustrated with practical examples.
Rule Zero, No Connection
For this to happen, the Global rule must be set to zero and the Local (application mnemonic) rule also set to zero. Every activity within this application is independent of INFO Option. change packages are created and carried through their life cycle without INFO Option ever being aware of their existence, unless there is a manual intervention or a batch (CMNSAS11) process to feed the information over.
Rules One to Five
Where the Globally and Locally set rules vary, the one with the higher number is enforced. At opportune moments (package Creation, Update, Freeze, Approval, Install, and Baseline Ripple), ChangeMan ZMF checks to see if the connection to the INFO Option subtask is attached. The following table provides descriptions for scenarios involving different combinations of package actions, INFO Option subtask statuses, and rule numbers.
| Package Action | INFO Option Subtask | Impact of INFO/Management Change Rules |
|---|---|---|
| Create | Detached | Liberal rules (1 or 2) allow the process to continue but warns a user that INFO Option was not updated accordingly. This processing without update was preauthorized by the Global and Local administrators by assignment of the rule. A more restrictive rule (3 to 5) would disallow the package to be created while the subtask is detached. It would be up to the ChangeMan ZMF and INFO Option administrators to decide the future course of action, e.g., loosen the rules or attach the subtask. |
| Create | Attached | Liberal rules (1 or 2) mean that a INFO Option change record is created with selected data fields from the package and the two are chained—the package logically points to the change record and the change record logically points to the package. The package field WORK REQUEST ID is where the INFO Option change record number is held. The INFO Option change record number is an eight-digit numeric field consisting of ● INFO field System Name (S0CA5) holds the 3 to 4 character application mnemonic. ● INFO field Key Item Affected (S0CBF) holds the package number. Rule 3 would act the same as 1 and 2. If this is a planned package, restrictive rules 4 or 5 would insist that an INFO Option change record previously exist essentially pre-authorizing the creation. For an unplanned package, rule 5 would have the same effect but rule 4 would be treated liberally, like rule 3. Pre-authorizing means ● A one-on-one chaining of package to INFO Option change record must happen. Package field Work Request ID must specify a unique INFO Option change record that has not already been chained to another package. If the INFO Option package hasn’t been created, the ChangeMan ZMF package creation process is suspended until the Info/Man package has been created. If the user specifies an Info/Man record that is not considered a change record (either syntax problem or configuration issue) or is already pointing to another package, appropriate messages to the user describe the offense until a valid chain is established or the package creation is canceled. |
| Update | Detached | Rule 1 is only concerned about creating packages, not updates. Rule 2 allows the process to continue but warns a user that INFO Option was not updated accordingly. Rules 3 to 5 would disallow the package to be updated until INFO Option subtask is re-attached. |
| Update | Attached | Rule 1 has no effect. Rules 2 to 5 would certify that all changes (within the subset of fields in common) are reflected in the associated change record. |
| Freeze | Detached | Rules 1 or 2 have no effect. Under rules 3 to 5, no attempt would be made to check if INFO Option had pre-approved the change record. |
| Freeze | Attached | Rules 1 or 2 have no effect. Under rules 3 to 5 ● Entity INFOMGMT is not on the approval list, no action is taken. ● Entity INFOMGMT is on the approval list, a check if the INFO Option approval status (Structure Word S0BF0) is A approved, or R rejected and that indication is captured. |
| Approve | Detached | Rules 1 or 2 have no effect. Under rules 3 to 5, no attempt would be made to check if INFO Option has approved the change record. |
| Approve | Attached | Rules 1 or 2 have no effect. Under rules 3 to 5 ● Entity INFOMGMT is not on the approval list, no action is taken. ● Entity INFOMGMT is on the approval list, a check if the INFO Option approval status (Structure Word S0BF0) is A - approved, or R - rejected and that indication is captured. |
| Complete (status TCC or BAS) | Detached | Under all rules, no attempt would be made to update INFO Option. The change package has cycled in a batch execution and there is no one to tell of the event. |
| Complete (status TCC or BAS) | Attached | Rule 1 has no effect. Rules 2 to 5 would certify that the change record status (Structure Word S0BEE) is changed to "CLOSED." |
Sample Change Package Creation
This section contains an example in which a real change package under ChangeMan ZMF is created. In this example, the INFO Option change record reference
Work request . . . . . . . . . 1907D92
is left blank. This is only legal if the INFO/Management Change rule is three or less (0 to 3). The intent is to create a new change record, link it to the new package and keep common data elements synchronized.
CMNCRT0R Create: Create a New Package
Option ===> __________________________________________________________________
L Long method S Short method
D No package description I No installation instructions
Package title
New fixes
Application . . . . . . . . . ACTP (Blank or pattern for list)
Requestor name . . . . . . . . Merylly
Requestor phone . . . . . . . 123-4567-890
Work request . . . . . . . . . 1907D92
Department . . . . . . . . . . IDD
Package level . . . . . . . . 1 (1. Simple 2. Complex
3. Super 4. Participating)
Package type . . . . . . . . . PLANNED (Planned or Unplanned)
Package time span . . . . . . PERM (Permanent or Temporary)
Package to copy forward . . . ________ (Optional package name)
Unplanned reason code . . . . ____ (\* for list)
Temporary change duration . . ____ (In days)
Notify user . . . . . . . .. . JDOE
Enter "/" to select option
_ Attach package to release
After the change package is created, a subsequent browse of package ACTP000024 will list the INFO Option change record number that has been assigned. Assume it is 00000123. It is now possible to view and/or update this information from INFO Option panels. Generally speaking, INFO Option panels are often customized. You accomplish data mapping through Structure Words, discussed later in this document (see "Structure Word Mapping").
Since we cannot predict the level of customization in force at any given shop, the following figures illustrate vanilla INFO Option change management panels only.
BLG0S020 CHANGE SUMMARY DISPLAY CHANGE: 00000123
Assignee name......... KDSW Change type............ SIM/PP
Assignee phone......... 555-5678 Change status.......... OPEN
Coordinator name...... PMXW Approval status........ PENDING
Program name........... ________ Owning priv. class...... _______
Device name............ ________ Entry priv. class....... CHGMAN
Key item affected...... 000024 Date entered............ 01/04/91
Date required......... 01/21/91 Time entered............ 22:47
Completion date....... ________ Date last altered...... 01/05/91
Current priority...... __ Time last altered...... 14:47
Estimated duration.... ________ User last altered...... CMNDSTAR
Description.......Payroll production abends with S0C7 on weekends.
SELECT ONE OF THE FOLLOWING, OR REPLY END OR CANCEL TO EXIT DISPLAY
1. Requester display. 6. Detail display.
2. Status display. 7. Activity list display.
3. Close display. 8. Approver display.
4. History display. 9. Reviewer display.
5. Freeform text and notes. 10. Record utilities.
===>
...
BLG0M100 CHANGE REQUESTER DISPLAY CHANGE: 00000123
Requested by............ DeBugger Change type............ SIM/PP
Requester dept.......... 0355 Change status.......... OPEN
Requester phone......... 555-1234 Approval status........ PENDING
Network name............ ________ Change reason........... ________
System name............. ABCD Initial priority....... __
Program name............ ________ Estimated duration..... ________
Device name............. ________ Problem fixed........... ________
Key item affected....... 000024 User form number........ ________
Date required.......... 01/21/91 Location code........... ________
Time required.......... 11:00
Description........Payroll production abends with S0C7 on weekends.
TO RETURN TO SUMMARY DISPLAY PANEL REPLY END OR CANCEL
===>
...
BLG0M200 CHANGE STATUS DISPLAY CHANGE: 00000123
Assignee name......... KDSW Change status.......... OPEN
Assignee dept......... CSW/TEAMZ Current phase.......... ______
Assignee phone......... 555-5678 Approval status........ PENDING
Date assigned......... 01/05/91 Planned start date..... ________
Time assigned......... 13:37 Planned start time..... _____
Transfer-to class..... ________ Actual start date...... ________
Current priority...... __ Actual start time....... _____
Coordinator name...... PMXW Planned end date....... ________
Coordinator dept....... ________ Planned end time....... _____
Coordinator phone...... ________ Estimated effort....... ____
Risk assessment....... ______ Estimated duration..... ________
Co-Requisites.......... ____________________________
Pre-Requisites......... ________________________
TO RETURN TO SUMMARY DISPLAY PANEL REPLY END OR CANCEL
===>
...
BLG0M500 CHANGE APPROVER DISPLAY CHANGE: 00000123
APPROVAL PENDING APPROVAL PROVIDED APPROVAL REJECTED
CHGMAN ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________
SELECT ONE OF THE FOLLOWING, OR REPLY END TO RETURN TO SUMMARY DISPLAY
1. Accept change for privilege class.
2. Reject change for privilege class.
===>
...
BLG0CU00 CHANGE REQUEST SUMMARY CHANGE: 00000123
Assignee name.......... KDSW Change status........... OPEN
Assignee phone......... 555-5678 Approval status......... PENDING
Coordinator name....... PMXW Current priority........ __
Device name............ ________ Owning priv. class...... ________
Key item affected...... 000024 Entry priv. class....... CHGMAN
Date required.......... 01/21/91 Date entered............ 01/04/91
Planned start date..... ________ Time entered............ 22:47
Completion date........ ________ Date last altered....... 01/05/91
Description............ Payroll production abends with S0C7 on weekends.
SELECT ONE OF THE FOLLOWING, OR REPLY END (TO FILE) OR CANCEL (NO SAVE)
1. Requester data. 6. Reviewer data.
2. Status data. 7. Activity entry.
3. Close data. 8. Freeform text.
4. Detail data. 9. File record.
5. Approver data.
===>
...
BLG0C100 CHANGE REQUESTER ENTRY CHANGE: 00000123
Enter change requester data; cursor placement or input line entry allowed.
1. Requested by....... DeBugger_______ 11. Change type......... SIM/PP__
2. Requester dept...... 0355_______ 12. Change status...... OPEN___
3. Requester phone..... 555-1234_____ 13. Change reason....... ________
4. Network name........ ________ 14. User change number.. 00000123
5. System name......... ABCD____ 15. Initial priority.... __
6. Program name........ ________ 16. Estimated duration.. ________
7. Device name......... ________ 17. Problem fixed....... ________
8. Key item affected... 000024__ 18. User form number.... ________
9. Date required....... 01/21/91 19. Location code....... ________
10. Time required....... 11:00
20. Description........ Payroll production abends with S0C7 on weekends.
WHEN COMPLETE REPLY END (TO SAVE) OR CANCEL (NO SAVE)
===>
...
BLG0C200 CHANGE STATUS ENTRY CHANGE: 00000123
Enter change status data; cursor placement or input line entry allowed.
1. Assignee name....... KDSW___________ 12. Change status...... OPEN___
2. Assignee dept....... CSW/TEAMZ__ 13. Current phase....... ________
3. Assignee phone...... 555-5678_____ 14. Planned start date.. ________
4. Date assigned....... 01/05/91 15. Planned start time.. _____
5. Time assigned....... 13:37 16. Actual start date... ________
6. Transfer-to class... ________ 17. Actual start time... _____
7. Current priority.... __ 18. Planned end date.... ________
8. Coordinator name.... PMXW___________ 19. Planned end time.... _____
9. Coordinator dept.... ___________ 20. Estimated effort.... ____
10. Coordinator phone... _____________ 21. Estimated duration.. ________
11. Risk assessment..... ______
22. Co-requisites....... ____________________________________________
23. Pre-requisites...... ____________________________________________
WHEN COMPLETE REPLY END (TO SAVE) OR CANCEL (NO SAVE)
===>
...
BLG0C500 CHANGE APPROVER ENTRY CHANGE: 00000123
Enter names of privilege classes that must approve this change request.
1. Approver priv. class... CHGMAN__ 10. Approver priv. class... ________
2. Approver priv. class... ________ 11. Approver priv. class... ________
3. Approver priv. class... ________ 12. Approver priv. class... ________
4. Approver priv. class... ________ 13. Approver priv. class... ________
5. Approver priv. class... ________ 14. Approver priv. class... ________
6. Approver priv. class... ________ 15. Approver priv. class... ________
7. Approver priv. class... ________ 16. Approver priv. class... ________
8. Approver priv. class... ________ 17. Approver priv. class... ________
9. Approver priv. class... ________ 18. Approver priv. class... ________
WHEN COMPLETE REPLY END (TO SAVE) OR CANCEL (NO SAVE)
===>
...