Step 47. Migrate Control-V

1. Modify the new Control‑V data set parameters
   1. If you want to change the parameters of the Control‑V Migrated User file, choose "Customize Control‑V User Files" in ICE Customization.
   2. Delete or rename the file.
   3. List all files with the %DBPREFD%.MIG* prefix. The list includes the DATA file and its extents, the INDEX file and its extents, and the DUAL files. Delete or rename all files in the list.
   4. Choose the "Format Migrate Users File" ICE minor step to recreate the Migrated user file using the new space parameters.
2. Migrate the Control‑V Migrated User file
   1. Run the CTDUFDUL job from the JCL library of the Control‑D version you are upgrading from, to back up the Migrated User files.
   2. Use the CTDUFRST sample job from the Control‑D current release JCL library to restore the files. For each file modify the necessary lines in the job.
3. Replace Control‑V procedures

   If you used Control‑V 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‑V JCL procedure prefixes are not the same as prefixes in the previous version, modify the JCL of the production jobs to refer to the new Control‑V JCL procedure names.

   If you modified any current release procedures during testing, modify the procedures in the MVS PROCLIB as well.

4. Adjust DB2 Global Index interface
   1. Run the CTDGBBPL job to create the DB2 Application plan and authorize it. This job is described in the discussion of the Control-D and Control-V Global Index Facility in the INCONTROL for z/OS Administrator Guide.
   2. Copy the CTDGIDB2 member from the previous Control-D PARM library to the current release Control-D PARM library. Ensure that the DB2 Application plan name specified in CTDGIDB2 is the same as created in step A.