Step 55. Final adjustments

1. (optional) Add the new release IOA LOAD library to the MVS Linklist.

   If the IOA LOAD library of the version you are now using was in the MVS Linklist and you want to permanently add the current release library to the list, edit the LNKLSTxx member in the SYS1.PARMLIB library, and add the reference to the new release IOA LOAD library.

   You may have to IPL to make the change effective. However, if you use a product that can dynamically modify the MVS Linklist, such as CA‑LOOK, you can skip the IPL.

   Note: If you commented out or removed STEPLIB DD statements from the IOA JCL procedures in the version you are now using, comment out the corresponding statements of the current release IOA JCL procedures. The STEPLIB DD statement is in the SIOAENV member in IOA PROCLIB. However, do not comment out STEPLIB DD statements from the Control‑O monitor procedure or the CMEM monitor procedure.

   BMC recommends that you comment out statements instead of removing them.

2. Modify COMMNDxx members to automatically start the installed products.
3. If subsystem names for the INCONTROL products have changed, modify IEFSSNxx members.
4. If you have products that enhance LLA performance, such as Quick‑Fetch or PMO, and you have disabled them during the upgrade, restart them.
5. Migrate Control-M/Server definitions in the Control-M/Enterprise Manager database from the earlier version to the new version by running the migrate_dc utility in the Control-M/Enterprise Manager environment. For more information on the migrate_dc utility, see the Control-M Migration Guide.
6. Re-implement previous customizations that were made to screens, exits, and so forth into the new environment.
7. Back up the entire IOA environment, including all new IOA and INCONTROL product libraries repositories, and definition libraries (for example, schedule, mission) owned by users.