Managing Staging Versions
Staging versions are managed with the Version Control panel. Using this panel, you can browse, compare, recover, delete, and view staging versions.
Version Control Panel
On the Stage: Package Component panel, type VC on the line command for a component.
CMNSTG01 STAGE: GENL000006 Components Row 1 to 10 of 10
Command ===>____________________________________________ Scroll ===> CSR
Name + Type Status Changed Procname User Request
___ GNLCPY00 CPY ACTIVE 20150106 180258 USER016
___ GNLSRC1A SRC ACTIVE 20150106 195420 *RECOMP* USER016
___ GNLSRC50 LOS ACTIVE 20150106 211617 *RELINK* USER016
___ GNLSRC99 SRC INCOMP 20150116 102220 USER016 LOCKED
___ GNLSRS00 SRS ACTIVE 20150106 194852 CMNCOB2 USER016
___ GNLSRS1B SRS ACTIVE 20150106 192057 *RECOMP* USER016
___ GNLSRS1C SRS ACTIVE 20150106 192124 *RECOMP* USER016
___ GNLSRS5A SRS ACTIVE 20150106 192150 *RECOMP* USER016
___ GNLSRS5B SRS ACTIVE 20150106 192214 *RECOMP* USER016
___ GNLSRS5C SRS ACTIVE 20150106 192228 *RECOMP* USER016
******************************* Bottom of data ********************************
...
The Version Control panel is displayed.
CMNSIDV1 Version Control Row 1 to 3 of 3
Command ===>__________________________________________ Scroll ===> CSR
Type: CPY Package: GENL000006 Staging view
Component: GNLCPY00 +
Level Prompt Changed User Description
___ STG _____ 2015/01/06 18:02 USER016 Test
___-001 _____ 2015/01/06 17:19 USER016 Checkout from baseline0
___ BAS _____ 2015/01/01 21:43 USER016 Baseline version
******************************* Bottom of data ********************************
...
You can also access this panel in display mode from the Source and Non-source categories of the Query Package function. This table describes the fields on the Version Control panel.
| Field | Description |
|---|---|
| Command | CANCEL: Cancel processing and exit the version control panel. Abbreviation: C |
| REFRESH: Display updated information on this panel. | |
LOCATE level: Scroll to row specified by level. For example: LOCATE - 025 |
|
| RESET: Clear all Line Command and Prompt fields. | |
| VIEW parm: Display a different view of the Version Control panel. Valid parm values include: | |
| STG: Display the component changed date, the UserID of the person who changed the component, and component change description. STG is the default view. | |
| SAVE: Display the staging version save date, the UserID of the person who changed the component, and the component change description. | |
| PROMO: Display the version promotion site, level, nickname and description. | |
| DIR: Display staging library directory size, date created, date changed and UserID. | |
| DIR2: Display staging library directory size, initial size, modified size, version number, modification level and UserID. | |
| The following parm values let you cycle through the Version Control panel views, which are presented in the sequence listed above. | |
| NEXT: Display the next view. | |
| PREV: Display the previous view. | |
| Type | Displays the library type of the component. |
| Package ID | Displays the ID of the package containing the component being processed. |
| Component | Displays the component name. |
| View | Indicates what view of the Version Control panel is displayed. See the View command above. Displayed values: |
| Staging view | |
| Save view | |
| Promotion view | |
| Directory view (1) | |
| Directory view (2) | |
| Line Command | Enter the line command for the action you want to perform against each version. |
| B: Browse a temporary copy of the staging version using ISPF Browse. | |
| C: Compare two staging versions and display a compare report. C must be entered on two versions listed on the Version Control panel. | |
| M: Merge 2 to 8 staging versions with the M+R Option. M must be entered on two to eight versions listed on the Version Control panel. | |
| D: Delete a staging version. (May only be used by administrators) | |
| R: Recover a staging version by copying the version to a user specified data set that is external to ChangeMan ZMF or to a ZMF package. Only saved staging versions (level -nnn) may be copied to a package. | |
| V: View a temporary copy of a staging version using ISPF View. | |
| Level | Displays the level for each version managed by staging versions. |
| STG Refers to the component in the package staging library. | |
| - Staging versions that were previously in the staging library, | |
| nnn listed in reverse chronological order by the changed or staged date. Level -001 is the most recently saved version. | |
| BAS refers to the component in the baseline library. | |
| Prompt | Displays the status of the last request against the component version. |
| VIEW STG: The fields below are displayed in the Staging view of the Version Control panel. | |
| Version saved | Displays the date and time that the component version was last modified or staged. |
| ID | Displays the TSO UserID or JOB name that last modified or staged the component version. |
| Description | Displays the component change description that was automatically created by ChangeMan ZMF or that was entered by the developer when the component was staged. |
| VIEW SAVE: The fields below are displayed in the Save view of the Version Control panel. | |
| Version saved | Displays the date and time that the staging version was saved. |
| Stamp | Displays the date/time stamp on the saved version in the staging versions VSAM file. |
| Description | Displays the component change description that was automatically created by ChangeMan ZMF or that was entered by the developer when the component was staged. |
| VIEW PROMO: The fields below are displayed in the Promotion view of the Version Control panel. | |
| Site | Displays the site to which the version was last promoted when it was the STG version. |
| Lvl | Displays the promotion level to which the version was last promoted when it was the STG version. |
| Nickname | Displays nickname of the promotion level to which the version was last promoted when it was the STG version. |
| Description | Displays the component change description that was automatically created by ChangeMan ZMF or that was entered by the developer when the component was staged. |
| VIEW DIR: The fields below are displayed in the Directory view of the Version Control panel. These ISPF statistics were recorded in the Staging Versions VSAM file when the member in the staging library was saved as a staging version. | |
| Size | Displays the number of lines of the saved version. |
| Created | Displays the date and time that the component version was created. |
| Changed | Displays the date and time that the component version was last modified or staged. |
| ID | Displays the TSO UserID or JOB name that last modified or staged the component version. |
| VIEW DIR2: The fields below are displayed in the Directory2 view of the Version Control panel. These ISPF statistics were recorded in the Staging Versions VSAM file when the member in the staging library was saved as a staging version. | |
| Init | Displays the initial size (number of lines) of the component version. |
| Mod | Displays the number of lines changed of the component version. |
| VV.MM | Displays the ISPF version number and modification level of the component version. |
| Per | The file permissions in octal format. |
| F | File format 0-7 |
| 0 Not specified | |
| 1 Binary data | |
| 2 New line | |
| 3 Carriage return | |
| 4 Line feed | |
| 5 CR & LF | |
| 6 LF & CR | |
| 7 CR & NL |
...
You can scroll through the list of versions and type line commands on one or more versions. After entering line commands, press Enter. Line commands are processed in the following order:
-
B (Browse), D (Delete), R (Recover) and V (View) commands are processed in the order that they appear in the version control list, top to bottom.
-
C (Compare) commands are processed next. The first version with a C line command (searching top to bottom) is processed as the “new” version, and the second version with a C line command is processed as the “old” version.
-
M (Merge) commands are processed last.
Recovering A Staging Version
Staging versions are recovered by copying the version to a data set that is external to ChangeMan ZMF or a package.
Copying a version to a data set
Note
You must have UPDATE security access to the target TO DATASET, and the UserID of the SERNET instance running ChangeMan ZMF must also have UPDATE authority.
Caution
Do not specify a package staging library as the target TO DATASET. If yourecover a staging version directly to a staging library, the overlaid member is not saved in staging versions, and package master records for the component are not updated.
-
On the Version Control panel, type R (Recover) on a line command for the version you want to recover.
CMNSIDV4 Copy Component Version Option ===> Package . . . . . GENL000006 Component . . . . GNLCPY00 + Type . . . . . . CPY Version . . . . . -001 1 Dataset To dataset 2 Package To package -
Select option 1 to copy the version to a data set.
The Copy To Dataset (CMNSIDV2) panel is displayed.
CMNSIDV2 Copy to Dataset Information Command ===>_________________________________________________________ Package . . . . . GENL000006 Component . . . . GNLCPY00 + Type . . . . . . CPY Version . . . . . STG To dataset . . . _______________________________________________________+This table describes the fields on the Copy To Dataset Information panel.
Field Description Package Displays the ID of the package containing the component being processed. Component Displays the component name. Type Displays the library type of the component. Version Displays the staging versions level selected for recovery. STG Refers to the component in the package staging library. -nnn Staging versions that were previously in the staging library, listed in reverse chronological order by the changed or staged date. Level -001 is the most recently saved version. BAS Refers to the component in the baseline library. To dataset The fully qualified data set name to which the recovered version will be copied. This is a data set outside of ChangeMan ZMF. -
Enter the name of the target data set and press Enter to execute the copy.
Copying a version to a package
Notes
Only saved staging versions (level -nnn) may be copied to a package.
A component version can be copied to the same or a different package and component.
-
On the Version Control panel, type R (Recover) on a line command for the version you want to recover.
CMNSIDV4 Copy Component Version Option ===> Package . . . . . GENL000006 Component . . . . GNLCPY00 + Type . . . . . . CPY Version . . . . . -001 1 Dataset To dataset 2 Package To package -
Select option 2 to copy the version to a package.
The Copy to Package (CMNSIDV5) panel is displayed.
CMNSIDV5 Copy to Package Command ===> Package . . . . . . . PETE000963 Component . . . . . . PJWA0000 + Type . . . . . . . JCL Version . . . . . . . -003 Target package . . . PETE000963 Target component . . PJWA0000 + Target type . . . . .JCL Change description . Enter "/" to select option / Confirm overlay Lock component / Save previous staging version Mixed caseThis table describes the fields on the Copy To Package panel.
Field Description Package The current change package. Component The name of the component to be copied. Type The library type of the component to be copied. Version The level number of the component version. Target package The package to copy the component to. Target component The name of the component to be copied to. If blank, thesource component name will be used. Target type The library type of the component to be copied to. Change description Describe the change being made to the component. If save staging versions is enabled, this description is displayed for each component version in the version control function. Lock component Select to lock the component in the target package. Omit to bypass locking the component. If the component is already locked in the target package, it will remain locked. Confirm overlay Select to view and respond to any confirmation required where the target file will be overlaid. Omit to bypass the confirmation panel. Save previous staging version Select to save the previous component version in the target package. This option applies only when the target library type 'Save staging version' option is set to 'PROMPT' and the component is already in the target package. Mixed case By default, all fields are folded to upper case. However, if the "Mixed Case" option is selected, the target component name is left as is. -
Select which options you want to use and press Enter to execute the copy.
Merging Staging Versions
When you type M in the Line Command for two to eight versions on the Version Control panel and press Enter, each selected version is copied to a separate temporary sequential data set, and your ChangeMan ZMF session is transferred to the M+R Option.
With the M+R Option, you can merge and reconcile multiple versions of a component, or multiple files, to create a single new version.
What you see first in the M+R Option depends on whether you used the M+R Option previously with this ChangeMan ZMF instance, either through the staging versions merge function or through option C (M+R Option) on the Primary Option Menu.
-
If the first M+R Option panel you see is the Member Reconciliation Menu panel, go to Member Reconciliation.
-
If the first M+R Option panel you see is the M+R Projects Repository panel, go to New M+R Option Users.
New M+R Option Users
If you have never used the M+R Option before on this instance of ChangeMan ZMF, the following M+R Projects Repository (SEROJECT) panel is displayed the first time you merge staging versions.
SEROJECT M+R Projects Repository
Command ===>
This panel displays only because the Merge+Reconcile installation has not been
completed successfully.
Press ENTER and ask your System Programmer to edit this SEROJECT panel.
You won't be able to use the project management facility - Option 5 PROJECT
and Option W Walk through M+R of the Primary Menu.
A SEQuential data set needs to be allocated with Record format FB, Record
length 80, Block size 6000, 1st extent 20 blocks, Secondary blocks 400.
All M+R users should have read/write access to this data set that will
contain information about the profiles of all team-oriented M+R Projects.
The fully qualified name of this data set needs to be set in the )INIT section
of this panel, as well as the fully qualified name of the M+R Samples dataset.
M+R Projects DSNAME . . .
M+R Samples DSNAME . . .
Each M+R project needs two profile data sets: one as an intermediate storage
("Work In Suspense" or WIS) and one for writing different M+R reports. The
preferred Unit Name and High Level Qualifiers for their allocation need to be
set in the )INIT section. Defaults are SYSDA and User logon ID, respectively.
WIS / Print Unit Name . . SYSDA
High Level Qualifiers . . CDFUSER
-
Read the Reconcile walkthrough for an overview of the M+R Option, and practice the line commands as instructed. To navigate the walkthrough panels, press PF8 to page down and PF7 to page up.
-
When you finish the tutorial, press PF3, or type End on the Command line and press Enter. Do this as many times as it takes to get back to the Version Control panel.
-
Maneuver to the following panel (from the primary option panel it’s C, M, 0 (that’s a zero) then 5 to display Profile Data Sets (SERDSNML) panel.
SERDSNML Profile Data Sets Command ===>_______________________________________________ WIS dsname . . . . . . . CMNTP.S6.MMR.WIS Print dsname . . . . . . CMNTP.S6.MMR.PRINT Export dsname . . . . . CMNTP.S6.MMR.EXPORT Export DSORG . . . . . . PDS (PDS, SEQ, PAN, LIB, or blank) Export member mask . . . ______ (Mask to rename Base members on export) LIB module name . . . . ______ (LIBrarian update module name: LIBR, LIBRARY)...
-
Fill in the appropriate data set names. If these datasets do not exist, ChangeMan ZMF will allocate them.
-
On the Version Control (CMNSIDV1) panel, select staging versions to merge by typing M on the Line Command for three to eight versions, then press Enter. The Merge+Reconcile (SER@PRIM) panel is displayed.
You are ready to proceed with Member Reconciliation.CMNSIDV1 Version Control Row 1 to 3 of 3 Command ===>__________________________________________ Scroll ===> CSR Type: CPY Package: GENL000006 Staging view Component: GNLCPY00 + Level Prompt Changed User Description M STG ______ 2015/01/06 18:02 USER016 Test ___ -001 ______ 2015/01/06 17:19 USER016 Checkout from baseline0 M BAS ______ 2015/01/01 21:43 USER016 Baseline version ******************************* Bottom of data ********************************
Member Reconciliation
Follow this procedure to merge and reconcile staging versions.
If you have used the M+R Option previously with this ChangeMan ZMF instance, the Member Reconciliation Menu (SER@MAIN) panel is displayed after you use the M+R option.
```
SER@MAIN Member Reconciliation Menu
Option ===>__________________________________________________
0 Profile Update user profile settings
1 Versions Specify base and derivative data sets and member names
2 Execute Execute (compare and merge) the specified versions of a file
3 Save Save the current reconciliation as "work in suspense" (wis)
4 Load Load prior "work in suspense" for edit now
5 Edit Resume editing the current reconciliation or just loaded wis
5P Print Print the last view (snapshot) of the reconciliation
6 Export Export a successful reconciliation effort to a file
6P Exp print Print a successful reconciliation effort
7 Analysis Analyze the progress and complexity of the reconciliation
7P Anl print Print analysis of the reconciliation progress and complexity
X Exit
```
-
On the Member Reconciliation Menu, choose Option 1 Versions and press Enter. The Versions (SERCDFCM) panel is displayed.
SERCDFCM Versions Command ===>____________________________________________________________________ CMN Export package: GENL000006 Libtype: CPY Export member: GNLCPY00 -Member--- Type Nickname Id Base: USER001.#DACAC13.#2395231.STG _________________ _____________ SEQ STG_____ -_ Last Member: or CMN appl/pkg: ___________ Libtype:___ _____________ ___ ________ __ Drv1: USER001.#DACAC13.#2395157.BAS _________________ _____________ SEQ BAS_____ A_ or CMN appl/pkg: ___________ Libtype:___ _____________ ___ ________ __ Drv2: _______________________________________________ _____________ ___ ________ __ or CMN appl/pkg: ___________ Libtype:___ _____________ ___ ________ __ Drv3: _______________________________________________ _____________ ___ ________ __ or CMN appl/pkg: ___________ Libtype:___ _____________ ___ ________ __ Drv4: _______________________________________________ _____________ ___ ________ __ or CMN appl/pkg: ___________ Libtype:___ _____________ ___ ________ __ Drv5: _______________________________________________ _____________ ___ ________ __ or CMN appl/pkg: ___________ Libtype:___ _____________ ___ ________ __ Drv6: _______________________________________________ _____________ ___ ________ __ or CMN appl/pkg: ___________ Libtype:___ _____________ ___ ________ __ Drv7: _______________________________________________ _____________ ___ ________ __ or CMN appl/pkg: ___________ Libtype:___ _____________ ___ ________ __Notice on the Versions panel:
-
The temporary data set created for each selected staging version is assigned to a base or derivative version in the M+R Option. The oldest staging version is assigned to the Base version on this panel, and the newest staging version is the derivative (Drvn) with the highest number.
-
The staging version Level is used as the version Nickname in the M+R Option.
-
The version ID in the M+R Option is an alpha character assigned in ascending order from the oldest derivative to the newest. (There is no ID assigned to the M+R Option Base version.)
On the Versions panel, you can change the files assigned to the Base and derivatives, and you can add derivatives that reside in other sequential or PDS files. You can change the Nicknames and the IDs assigned to versions on this panel.
-
-
When you are satisfied with the entries on the Versions panel, press PF3 or type End on the Command line and press Enter, to return to the Member Reconciliation Menu.
-
On the Member Reconciliation Menu, choose Option 2 Execute. The Reconcile (CDFPANEL) panel is displayed.
CDFPANEL ------------------------- RECONCILE --------------- ROW 1 TO 20 O Command ===> Scroll ===> A:SOURCE#A ******************************** TOP OF DATA ***************************** 000000 ********/* 2015/03/13 09:02:08 CMNTP.S6.V810.BASE.ACTP.SRC 000001 IDENTIFICATION DIVISION. 000002 PROGRAM-ID. ACPSRCCE. 000003 > A___ *PACKAGE ACTP000038 S6.V810 000004 *PACKAGE ACTP000076 S4.V712 ERO S4712COM RELATED COMM 000005 *PACKAGE ACTP000001 S6.V810 000006 000007 ENVIRONMENT DIVISION. 000008 CONFIGURATION SECTION. < 0009 SOURCE-COMPUTER. IBM-370. <>A___ SOURCE-COMPUTER. TRS-80. < 0010 OBJECT-COMPUTER. IBM-370. <>A___ OBJECT-COMPUTER. HP-3000. 000011 000012 INPUT-OUTPUT SECTION. 000013 FILE-CONTROL. 000014 000015 DATA DIVISION. 000016 WORKING-STORAGE SECTION -
Merge and reconcile the Base and derivative versions. Press PF1 for Help.
-
To end your reconciliation session and return to the Member Reconciliation Menu, press PF3 or type End on the Command line and press Enter. When you exit your session, the results of your reconciliation are saved in your WIS file
-
If you exit from the M+R Option, the temporary data sets created by staging versions are deleted.
-
To resume the reconciliation effort from your WIS file:
-
On the ChangeMan ZMF Primary Option Menu, select Option C M+R.
-
On the Merge+Reconcile panel, choose Option M Reconcile.
-
On the Member Reconciliation Menu, choose Option 4 Load.
-
On the Member Reconciliation Menu, choose Option 5 Edit.
-
-
To export the results of your reconciliation into your M+R Option Export file, choose Option 6 Export on the Member Reconciliation Menu.
-
To see the data set name of your Export file:
-
Choose Option 0 Profile on the Member Reconciliation Menu to display the Profile panel
-
Choose Option 5 Datasets to display the Profile Data Sets panel.
-
-
After you export the reconciled component into your Export file, use one of these methods to get the new version into your change package:
-
Stage the component from development to overlay the staged version.
-
From inside an edit-in-stage session, delete all of the lines, then use the COPY command to copy all lines from the new version.
-