Skip to content

Applying Maintenance Releases

This appendix discusses the procedures for applying a maintenance release to an existing ChangeMan instance.

Introduction

For any ChangeMan ZMF maintenance release, there are some customary actions that you execute to apply changes to your existing ZMF instances.

This Appendix describes those tasks. See the Readme for tasks that apply to the specific maintenance release you wish to install.

Updating Delivered Libraries

The ChangeMan ZMF installer for this maintenance release contains both the Full version and the Patch version of the maintenance release software. When you run the installer, you are prompted for the version that you want to install.

  • The Full version contains all components for ChangeMan ZMF, including components that are new and changed in maintenance releases since the major version release.

    If you are upgrading from a prior version you must install the Full version. For example, if you are currently running ZMF 7.1.x and want to install ZMF 8.2 Patch 1, you must install the Full version.

  • The Patch version contains only those components that are added or changed in maintenance releases since version 8.2.

    If you are upgrading from ZMF 7.1.x to ZMF 8.2 Patch 1, you must install the Full version.

Note

Maintenance releases contain all patch releases since the last maintenance release.

Execute these steps to update your delivered libraries with components changed in the maintenance release:

  1. Before you update your delivered libraries, make a copy of your current delivered libraries to use in a later task.

  2. If you are installing a Patch version, copy the contents of the maintenance release libraries into your delivered libraries, replacing like-named members.

  3. If you are installing a full version, replace your current delivered libraries with the maintenance release libraries.

Updating Custom Libraries

The ChangeMan ZMF Installation Guide tells you to allocate these custom libraries.

CMNZMF SERCOMC
ASMSRC ASMSRC
CLIST LOAD
CMNZMF SERCOMC
CNTL
PANELS
LOAD
MESSAGES
REX
SKELS

After you update your delivered libraries, follow this procedure to update your custom libraries:

  1. Allocate a new set of custom libraries.

  2. Copy any custom components that are all original code into your new custom libraries.

  3. If you use the ChangeMan ZMF M+R Option:

    1. On the Versions panel, define your base and derivative libraries as follows:

      Base: Delivered library for old version

      Drv1: Custom library for old version

      Drv2: Delivered library for new version

    2. On the Consolidation Workplace panel, reconcile your old customization with the new maintenance release components.

    3. When you have reconciled all of your customization, export reconciled components to your new custom library.

  4. If you do not use the ChangeMan ZMF M+R Option:

    1. Determine what components are changed in the maintenance release by comparing delivered libraries before and after updates for the maintenance release.

    2. Find components in your custom libraries that are changed in the maintenance release.

    3. Determine whether your modifications will be valid in the maintenance release.

    4. Copy the new delivered version to a new custom library and reapply your modifications.

  5. Assemble custom source members into your custom load library.

Important

Some changes in a maintenance release may make your modifications obsolete or require you to change your modifications.

Managing Copybook Changes

Occasionally, copybooks delivered in the CMNZMF ASMCPY library or the SERCOMC ASMCPY library are changed in a maintenance release.

Follow this procedure to discover copybook changes and rebuild load modules as necessary.

  1. Compare you current delivered copybook libraries to the libraries delivered in the maintenance release.

    1. CMNZMF ASMCPY

    2. SERCOMC ASMCPY

  2. If you customized exit programs in the CMNZMF ASMSRC library or the SERCOMC ASMSRC library that use a copybook that has changed, assemble those exits using copybook libraries from the new release, even if you do not change your customization in the program source.

    ASMCPY members CMNEX* and SEREX* are included in the ASMSRC members with the same name. For example, copybook CMNEX001 is contained in source member CMNEX001. So, if copybook CMNEX001 is changed, you must reassemble a customized exit CMNEX001.

  3. The SERCOMC ASMCPY library contains COBOL copybooks with member names XMLC****. If you have written custom COBOL programs that use XMLC**** copybooks that have changed in the new release, recompile those custom programs using copybook libraries from the new release, even if you do not change your COBOL program source.

Binding Db2 DBRMs

If you license the ChangeMan ZMF Db2 Option, or the ERO Option, or use Db2 for the baseline I/A table, you must bind any relevant changed DBRMs delivered in a maintenance release. For more information, see the Db2 Getting Started Guide.

This table lists all Db2 DBRM delivered with the ChangeMan ZMF Db2 Option and the ERO Option.

DBRM Option BIND JCL Function
CMNAD901 Baseline I/A CMNDB2IA Pkg audit access to Db2 hosted I/A
CMNDB2AD DB2 DB2OPTN Db2 Option (non-core)
CMNDB2AT DB2 DB2OPTN/R Db2 Option (non-core)
CMNDB2IA Baseline I/A CMNDB2IA General access to Db2 hosted I/A
CMNDB2RI ERO with Baseline I/A CMNDB2IA/RP ERO access to Db2 hosted I/A
CMNDB2RQ ERO CMNDB2RP Release management
CMNDB2SQ DB2/ERO BINDPKG Db2 option PLAN lookup
CMNDB2VB DB2 DB2OPTN Db2 Option
CMNRACHK ERO CMNRAUTB Check ERO I/A table
CMNRAHAR ERO CMNRAUTB Shrink history table
CMNRARPT ERO CMNDB2RP Release audit
CMNRARTM ERO CMNDB2RP Release audit
CMNRASUM ERO CMNDB2RP Release audit
CMNRA905 ERO CMNDB2RP Release audit
CMNRA906 ERO with Baseline I/A CMNDB2IA/RP Release audit (access to baseline I/A)

Important

The DBRM for CMNDB2SQ must be bound into Db2 packages in all Db2 subsystems where the ChangeMan ZMF Db2 Option performs binds or manages stored procedures, user defined functions, or triggers. Refer to the Db2 GSG for further details on bind requirements.

If your library compares indicate that DBRMLIB members are changed in the maintenance release, take these actions:

  1. If you license the Db2 Option, follow the instructions in the ChangeMan ZMF Db2 Option Getting Started Guide to bind changed SQL into a Db2 package.

  2. If you license the ERO Option, follow the instructions in the ChangeMan ZMF ERO Getting Started Guide to bind changed SQL into Db2 packages.

Note

DBRM for ChangeMan ZMF programs are created with Db2 precompiler parameter VERSION(AUTO), so you can bind the SQL before you actually install the load modules for the new versions of the programs.

Managing XML Services Changes

Most ChangeMan ZMF functions are executed by XML Services, even when you use the ISPF interface.

Follow this procedure to upgrade XML Services for the new release unless the Readme tells you that XML Services have not changed and that the procedure is not required.

  1. If you are currently using XML Services and/or have written programs that use XML Services, contact Support for a version of the XML Delta Report that identifies which XML Services have changed between your current release and the new maintenance release. Use this report to determine if you are using any of the XML Services that have changed, and then plan this part of your upgrade accordingly.

  2. Run the job in member XMLLOAD in your custom CNTL library to delete, define, and reload the XMLSPACE VSAM LDS and the MAPDATA sequential file with the new data in member XMLDATA in the delivered SERCOMC CNTL library.

Note

Load the new data at the same time that you start using the new load modules delivered with the release. If you back out the upgrade, restore the previous contents of the XMLSPACE VSAM LDS and the MAPDATA sequential file.

Synchronizing Impact Analysis Data

To ensure the integrity of the audit function, run a full impact analysis maintenance process after you apply the maintenance release. See topic "Generating and Updating Impact Analysis Data," in Chapter 4, "Setting Up Global Administration" in the ChangeMan ZMF Administrator’s Guide.

Updating Housekeeping Jobs

Updates to ChangeMan ZMF components sometimes result in changes to the sample JCL delivered in the CNTL file.

If you have built housekeeping jobs from the sample JCL in the CNTL library, follow this procedure to update your housekeeping jobs:

  1. Compare the delivered CNTL library for your current ChangeMan ZMF release to the delivered CNTL library for the new release.

  2. Use the table in topic "Sample JCL / Housekeeping Job Cross Reference" at the end of the "Batch Housekeeping Tasks" chapter in the ChangeMan ZMF 8.1.2 Administrator’s Guide to see what housekeeping jobs use the sample JCL that has changed.

  3. Update your housekeeping jobs with the changes in the sample JCL in the new release.