Step 48. Migrate Control-O

Note: If you rename the Control‑O monitor during testing or switch over to production, rename the CTOSERV server procedure in a corresponding manner. For example, if you named the Control‑O monitor CONTROLO, name the server procedure CTOSERV. Otherwise, the Control‑O monitor and the server procedure will have the same 3‑character prefix.

1. If you used Control‑O 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‑O is started under the master scheduler rather than under JES, copy the procedures for the Control‑O monitor and server into SYS1.PROCLIB or to any library pointed to from MSTJCLxx in use in the SYS1.PARMLIB.

   If Control‑O 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‑O JCL procedure names.

2. If you renamed the new Control‑O monitor and server procedures during testing, give them their production names.
3. If Control‑O/COSMOS is installed, or the Global Variables database is used, verify that the IOA Global Variables files (DD statements DAGRPD/I DAVAMD/I and DAVAAD/I) are allocated.
4. For each system where Control-O is installed, copy the members from the Control-O Global Variables Library (&OLPREFO..GLB.CPUsmfid) from the earlier version to the Control-O Global Variables Library (&OLPREFO..GLB.CPUsmfid) of the new version.

   If necessary, use ISPF option 3.3 or the IEBCOPY utility to copy the members.

5. Adjust the Control‑O RULELIST.

   Ensure that the RULELIST member in the Control‑O current version Parameters library references the correct rule definitions in the correct Rules libraries.

   If you are using Control‑O/COSMOS, add the COSMOS table to the RULELIST member. The COSMOS table is shipped in the Control‑O Rules library.

   If the Control‑O Communications facility is installed, add the CTOGATEI table to the RULELIST member. The CTOGATEI table is shipped in the Control‑O Rules library.

   If you are using CMEM functions, ensure that the IOACMEML member in the current version Parameters library references the correct rule definitions in the correct Rules libraries.

6. Adjust Control‑O DAGLBLST.

   Verify that the DAGLBLST member in the Control‑O current release Parameters library references the correct GLOBAL variable pools in the Control‑O GLOBAL variable libraries and databases.

   If you are using Control‑O/COSMOS, add the COSMOS databases to the DAGLBLST member.

7. Verify that an Automation Log exists.

   If the file has not been allocated because the Automation Log was allocated to an active Control-O monitor during installation, perform the below steps

   1. Use the IDCAMS utility to delete or rename both the CLUSTER and the DATA elements of the existing Automation Log files in each computer that is running Control-O.
   2. Enter the main ICE screen.
   3. Select Customization.
   4. Select an environment to customize.
   5. Enter CTO in the Product field.
   6. Select Product Customization.
   7. Select major step 2, "Customize Control-O Dataset Parameters."
   8. Select minor step 6, "Allocate the Automation Log File."
   9. Submit and execute the job on every system that should run Control-O.
8. If you have installed Control‑O/COSMOS or you intend to use the Control‑O GLOBAL variable database, verify that the Control‑O monitor procedure uses the correct names of the database files.

   Note: The Control-O monitor can be restarted at this point. After Control-O has been initialized, you can restart any other INCONTROL products for which all migration steps have been completed.