Step 50. Migrate Control-M/Tape

1. Replace Control‑M/Tape procedures.

   If you used Control‑M/Tape procedures in your jobs you can use JCLLIB statement or you can copy these procedures to the procedure library at your site.

   Note: If Control‑M/Tape JCL procedure prefixes are not the same as prefixes of the previous version, modify the JCL of the production jobs to refer to the new Control‑M/Tape JCL procedure names.

2. If the Control‑M/Tape Repository file attributes used for the testing phase need to be changed, modify the new Control‑M/Tape data set parameters. Changes in these parameters affect the allocation and formatting of Control‑M/Tape data sets. You can modify values and customize formatting jobs by using the "Customize Control‑M/Tape Datasets" major step in ICE Customization.

   Complete the remaining minor steps in ICE. These steps update the file definition statements and the DEFPARM member so that the formatting jobs are customized and ready for submission in later steps.

3. If you are going to use the Media database of your previous Control‑M/Tape version, and that database is shared by other systems, ensure that the DBPREFT ICE variable and DBPREF parameter in CTTPARM have the same value as in the previous version.
4. Upgrade Media Database and Stacking Database

   In "CTT Customization" in ICE, select the "Upgrade Control‑M/Tape Repository" major step, and perform its minor steps.

   Select the "Adjustments" major step, and perform the "Building Vault Information in MDB" minor step.

5. Using static installation

   While running in TEST mode, you cannot statically install the Control-M/Tape SVC and MVS Tape Label Processing Exits. For more information, and to help you determine whether you want to proceed with a static installation, review the description of ICE minor steps "Control-M/Tape SVC Installation." and "MVS Tape Label Processing Exits Installation" in the INCONTROL for z/OS Installation Guide: Installing.

6. Initialize Control‑M/Tape.