Skip to content

Sample Conversion Day Script

A conversion-day script lists all of the tasks that you must complete on the day that you convert a ChangeMan ZMF instance to version 8.3.

The conversion-day script is one of the last steps in your migration plan. See Model Migration Plan for an example of a migration plan.

Note

The model conversion-day scripts shown in this section are meant to be embedded within the model plan in the previous section. There are important conversion steps that are in the plan rather than the script because those steps can be executed before the actual day of conversion.

Conduct dry-run tests of your script with copies of production data to validate space allocations and to establish expected run times for each step.

The following list of tasks is an example of the kind of tasks that you should include in your conversion-day script for upgrading a ChangeMan ZMF instance to version 8.3. Detailed instructions for these tasks are provided in one of the following chapters, as appropriate to the release that you are upgrading:

Review this sample conversion-day script and write scripts that fit your implementation of ChangeMan ZMF:

  1. Verify that vendor libraries for ChangeMan ZMF 8.3 are installed in production.

  2. Verify that the change package containing the following version 8.3 custom components is installed in ChangeMan ZMF 8.3 production libraries:

    • Load modules for customized exit programs.

    • Customized messages.

    • Customized panels.

    • Customized REXX programs.

    • Customized skeletons.

    • Customized and generated tables (including CMNKEYS).

    • Recompile HLL exits that are written in an LE language, ensuring the recompile uses the new versions of copybooks.

  3. Stop the started task for the ChangeMan ZMF version that you are migrating.

  4. Use existing pre-conversion housekeeping jobs or other JCL to back up the following VSAM files in your production environment:

    1. Package Master

    2. Component Master

    3. Impact Analysis File

    4. Delay File

    5. Staging Versions VSAM files

  5. Use existing pre-conversion housekeeping jobs or other JCL to back up and clear the following log and recovery files in your production environment:

    1. Activity Log File

    2. Recovery File

    3. Impact Analysis Recovery Log

    4. Component Master Recovery Log if applicable (7.1.2.01 or before)

  6. For customers who license the ChangeMan ZMF ERO Option, unload or image copy the release management Db2 tables.

  7. Execute the procedure to convert your Package Master, Component Master, (and Saved Staging Version) data sets.

  8. Execute the procedure to create and load your ChangeMan ZMF XMLSPACE LDS.

  9. For customers who license the ChangeMan ZMF ERO Option, perform the following actions as required:

    1. Execute the procedure to expand ERO release audit and release management Db2 tables.

    2. Unload or image copy the release management tables, and bind ERO DBRMs in your production environment.

  10. Install the change package containing the following components into system libraries:

    1. Sernet started procedure.

    2. JCL for started procedure CMNxADSP and/or the procedures you created for:

      • Installation (X.node) JCL build.

      • HLLX started task procedure if used.

      • Batch component build.

      • Promotion JCL build.

      • Other jobs that are file tailored.

    3. Log-on CLIST.

    4. INCLUDE group updated with ChangeMan ZMF 8.3 libraries for installation jobs that were file tailored under the ZMF release that you are migrating.

    5. Housekeeping JCL and cataloged procedures.

  11. Use version 8.3 housekeeping jobs to back up the following converted VSAM files in your production environment:

    1. Package Master.

    2. Short Name Component Master.

    3. Long Name Component Master.

  12. Bring up the new Sernet started task that you defined for ChangeMan ZMF 8.3.

  13. If you change library type definitions or baseline library names in application administration, execute the procedure to synchronize the impact analysis data.

  14. Run post-conversion test scripts to validate version 8.3 functions, custom modifications, and administration entries prior to releasing the system to developers for use.