Applying Maintenance Releases

This appendix discusses the procedures for applying a maintenance release to an existing dedicated ZDD server.

Introduction

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

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

Updating Vendor Libraries

ChangeMan ZDD server libraries for a maintenance release are delivered as a full product libraries. There are no "fix" level libraries that contain only the components changed for the maintenance release.

Execute these steps to update your SERCOMC vendor libraries with components changed in the ZDD maintenance release:

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

2. Replace your current vendor libraries with the maintenance release libraries.

Updating Custom Libraries

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

...SERCOMC.VvRrMm.CUSTOM.ASMSRC

...SERCOMC.VvRrMm.CUSTOM.CLIST

...SERCOMC.VvRrMm.CUSTOM.CNTL

...SERCOMC.VvRrMm.CUSTOM.LOAD

After you update your vendor 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 can use the ChangeMan ZMF M+R Option:

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

   • Base: Vendor library for old version

   • Drv1: Custom library for old version

   • Drv2: Vendor library for new version

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

   c. 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:

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

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

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

   d. Copy the new vendor 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 will make your modifications obsolete or require you to change your modifications.

Reloading XMLSPACE VSAM LDS

If the Readme recommends that you reload the XMLSPACE LDS, 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.

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.