Skip to content

Staging Versions

The staging versions facility can save an unlimited number of versions of a package component that a developer might create in a staging library between the time the component is first added to the package and the time the package is baselined.

Staging versions may be created only for components that can be edited from the Stage: Package Components panel.

Staging versions are stored as full copies in a compressed format in a VSAM file. Each version may be labeled with an optional 35-character description.

Some features of staging versions are available if the merge facility has been installed. The merge facility of staging versions is only available if your company has licensed ChangeMan® M+R.

Staging Versions Installed

For detailed SSV implementation instructions, See Step 6: Define Staging Versions VSAM Files and Step 10: Build SERNET JCL for ChangeMan ZMF in Chapter 5 of the ChangeMan ZMF Installation Guide.

These features are available if the staging version facility has been installed:

  • The VC Staging Selection Code can be used to display the Version Control panel for any component that is on the Stage: Package Components panel.

  • The Version Control panel always shows a STG version and usually a BAS version. These versions are pointers to the component in the staging library and baseline library respectively.

  • From the Version Control panel, the STG and BAS versions can be browsed, viewed, and compared.

Staging Versions Enabled

The staging versions facility may be enabled for a library type by setting the Save Staging Versions parameters in Global and Application Library Types.

These features are available in library types for which the staging version facility has been enabled.

  • Users can add a component change description each time they create a new version of a package component on the Stage: Package Components panel.

  • Users can save a staging version whenever they change a component on the Stage: Package Component panel.

  • The administrator can make ChangeMan ZMF create a staging version every time a staging library member in the enabled library type is changed, or ChangeMan ZMF can ask if the user wants to overlay the component in the staging library without first creating a staging version.

  • From the Version Control panel, the user can browse and view staging versions.

  • Users can compare any two staging versions listed on the Version Control panel.

  • Administrators can delete staging versions listed on the Version Control panel.

...

ChangeMan® M+R Licensed

If your company licensed ChangeMan M+R, and your administrator installed the software, you can merge two to eight versions listed on the Version Control panel to create a new version of the component. ChangeMan M+R is automatically invoked, and the Base and derivative versions are automatically assigned.

Considerations For Staging Versions

You must consider the following issues before you decide to install or enable save staging versions:

  • If the staging versions facility is installed, ChangeMan ZMF reads one of the staging version VSAM files whenever a user performs a function that replaces a member in a staging library. This VSAM read might have an adverse effect on ChangeMan ZMF response time.

  • If the staging versions facility is installed and enabled for a library type, ChangeMan ZMF writes to the save staging version VSAM files whenever a user saves a staging version. This VSAM write might have an adverse effect on response time.

You can disable staging versions for a library type by changing the Save Staging Versions parameter to NO in the library type definition in Application Parameters.

You can de-install the staging package facility by removing the HPSPLIB and HPSIN DD statements from the SERNET started task JCL. You can then delete the three staging version VSAM files.