Defining Package Control Information
The first panel displayed in the Create Package process is the Create: Create A New Package panel (CMNCRT0R).
CMNCRT0R Create: Create a New Package
Option ===>____________________________________
L Long method S Short method
D No package description I No implementation instructions
Package title
Demo package-----------------------------------------------
Application . . . . . . . . . DEMO_ (Blank or pattern for list)
Requester's name . . . . . . John Doe_______________________
Requester's phone . . . . . . (555)_555-5555_
Work request . . . . . . . . .____________
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
This table describes the fields and options available on the Create: Create A New Package panel.
| Field | Description |
|---|---|
| Option | Choose a method for creating your package. See Package Description Methods |
| Long method | L: Show all panels in the Create Package process, require input for text descriptions. All package creation panels will be displayed for required user input, including Package Description and Implementation Instructions. |
| Short method | S: Create a package using the SHORT method: only the first and last panels will be displayed. |
| No package description | D: Use Default Package Description Omit the display of panel CMNCRT02 (Package Description) but still display the other panels. Package description will be 'NONE'. |
| No implementation instructions | I: Use Default Implementation Instructions. Omit the display of panel CMNCRT03 (Implementation Instructions) but still display the other panels. Implementation Instructions will be 'NONE' |
| Package title | Enter free-form text to identify this package. |
| Application | Enter a valid 3 or 4 character application mnemonic, as established by your ChangeMan ZMF Administrator. ChangeMan ZMF will assign a sequential number as part of the Package ID. You must have UPDATE access to this mnemonic in your security system. |
| Requester’s name | Enter your name or the name of the person requesting this change package. This field is not case sensitive and has a maximum length of 25 characters. |
| Requester’s phone | Enter a telephone number (extension) for the person whose name you entered in Requestor Name. This field has a maximum length of 15 characters. |
| Work request | This field may be required by your Administrator. Also, depending upon the INFO MANAGEMENT RULE currently in effect, this number may be tied to an INFO Change Record number. This field has a maximum length of 12 characters and is not case sensitive. |
| Department | Enter the department for this change package if required. This field is used for reporting only. This field is not case sensitive and has a maximum length of 4 characters. |
| Package level | Enter a one-character code (1-4) representing the package level. Note: If you 'copy forward' an existing change package to create this one, its 'level' will be copied also. |
| 1. Simple - The change package contains a change that is unrelated to any other change package. This level of change package does not affect any other application, nor does it require changes to software or operational procedures in other applications. | |
| 2. Complex - The parent for two or more participating change packages that have interdependent changes to software or operational procedures. To create a super or complex package, you provide only this first panel of control and general information, a package description, and a list of participating packages. Remote sites and installation dates are set in each participating package. No staging libraries are allocated to super or complex packages. There are no processing difference between super and complex change packages. | |
| 3. Super - The "parent" for change packages that contain major changes to several applications. To create a super or complex package, you provide only this first panel of control and general information, a package description, and a list of participating packages. Remote sites and installation dates are set in each participating package. No staging libraries are allocated to super or complex packages. There are no processing difference between super and complex change packages. | |
| 4. Participating - The change package is related to one or more other participating change packages which are listed under the same super or complex package, otherwise it is much like a Simple package. SYSLIB statements in build process jobs include staging libraries from other participating packages under the same super or complex package. | |
| Package type | Choose a package type. P: PLANNED - The package contains PLANNED change. These are change packages that have been previously scheduled. (Abbreviation: P) U: UNPLANNED - The package contains UNPLANNED changes. These packages are commonly referred to as “emergencies” or “emergency fixes” and are unscheduled. Depending on Global and Application Administration settings, some package lifecycle steps and requirements may be skipped. (Abbreviation: U) |
| Package time span | Choose a package time span. P: PERMANENT - Package components are installed in baseline and production libraries. A permanent package may be either planned or unplanned. Super, complex, and participating packages must be permanent. (Abbreviation: P) T: TEMPORARY - Changes are installed in special override libraries concatenated on top of your production environment library concatenations. These changes may be special one-time or short-term processing and are removed from these libraries after the Temporary Change Duration has passed. Baseline and production libraries are not changed. A temporary package may be either planned or unplanned. You must provide a Temporary Change Duration on this same panel. (Abbreviation: T) |
| Package to copy forward | Enter Package ID that you want to use as a model for the package you are creating. Package control and descriptive information from the model is displayed on create package panels for your new package, and a list of the components in the model are copied into your package. See Package Description Methods |
| Unplanned reason code | Enter the 3-digit change reason code that best represents why you are installing an unplanned change package. These codes were established by your ChangeMan Administrator. Enter '*' to display a reason code selection list. |
| Temporary change duration | The number of days that changes in temporary packages are to remain in override libraries. Valid days are 1-999. The count of calendar days for Temporary Change Duration is incremented at 23:59 system time each night. Temporary package components are automatically removed at the time-of-day specified in the Install Date/Time. Therefore, the number entered in Temporary Change Duration does not necessarily equate to 24- hour days. For example, a temporary package has an Install Date/Time of 20041015 / 1800, a Temporary Change Duration of 1, and the package is actually installed at 2100 on the install date 10/15/ 2004. Package components are automatically removed from temporary libraries at 1800 on 10/16/2001, which is less than 24 hours after they were installed. |
| Notify user | Enter the TSO userid of the user to be notified of major package changes, such as when the package is frozen. If not specified, this defaults to the package creator. |
| Attach package to release | Enter (/) to attach this change package to a release. When selected another panel will be displayed where you will select the release that this package will be attached to. |
When you finish typing information on the Create: Create A New Package panel, press
Enter. If no error message are displayed, the next panel in the create package process is
displayed. Your new change package is not created until all new package information has been entered and validated.