Step 14. Adjust the IOA component

The topics described in this step refer to IOA and the INCONTROL products installed at your site. Specific adjustments appear in the step for each product.

Apply the adjustments to the version you are now using, to the current release IOA component as follows:

1. Adjust exits and security modules

   For information about the exits, see "IOA Exits" in the Exits chapter in the INCONTROL for z/OS Administrator Guide. For information about security modules, see the INCONTROL for z/OS Security Guide.

2. Adjust security definitions
   • Grant permission to production users to access their data sets.
   • If the new IOA QNAME differs from that in the previous IOA production environment, modify the security definitions accordingly. For more information about the security entity structure that IOA and INCONTROL products use to validate authorization for each particular function, see the INCONTROL for z/OS Security Guide.
   • Adjust CLISTs, ISPF panels, ROSCOE RPFs, and procedures.
3. Adjust messages and screens

   For information about modifying messages and screens, see the IOA Administration chapter in the INCONTROL for z/OS Administrator Guide.

4. Adjust Dynamic Destination table

   The IOADEST member in the IOA.PARM library now contains the Dynamic Destination table, replacing the CTMDEST load module. The IOAGDST utility can be used to convert a CTMDEST load module to a IOADEST member. For more information see the Dynamic Destination Table section in the IOA Shout facility section in Setting rules - Jobtrac Mainframe editor.

5. Adjust KSL report programs and utilities

   Because of changes to screen layouts in the current release, you may need to adjust locally developed KSL scripts.

6. Adjust profiles

   Specify values for profile variables following the Customization procedure in ICE, using profile variable values in your current IOA production system as a reference. Values entered in ICE are stored in the $PROFMOD member in the IOA.PARM library.

   To use the old profile values for a specific user, in the new environment, copy the user profile from the previous environment’s IOA.PROF library to the new IOA.PROF library.

   Note: BMC recommends that you specify profile variables for all relevant INCONTROL products at the same time.

7. Modify libraries

   Make modifications to the IOA BANNERS library and to the following Control‑D libraries:

   • ACIFPARM
   • APAPARM
   • DJDEPARM
   • FTOPARM
   • OUTPARMS
   • SKL
   • TRANSTO

   All definitions and libraries created in the version you are now using can be used without change in the current release.

   If reports with names between 20 and 50 characters long will be used, the corresponding members in these libraries should be created in accordance with the format described in the INCONTROL for z/OS Administrator Guide.

8. Special options
   • If you are using the IOA Online monitor CICS interface and a CICS version earlier than 3.3, apply Optional Wish WI0787.
   • If you are using the IOA Online monitor or the IOA VTAM monitor interface, note the following:

   —The built-in capabilities of a terminal that can be queried determine its color and size attributes. (A terminal that can be queried is one that has a LOGMODE that supports either EXTENDED DATA STREAM or GENERIC in the PSERVIC definition.) For example, a terminal that is able to display color does so even if the terminal is defined as monochrome in the LOGMODE.

   —If you want the terminal to use color and screen size attributes that are not based on its actual capabilities, do one of the following:

   • Activate optional Wish WI0310. This forces the IOA VTAM monitor to use the color attributes of the ICOLOR parameter in the terminal's IOA PROFILE for all the terminals that log into the IOA VTAM monitor. Screen size is determined by the terminal's LOGMODE PSERVIC definitions.
   • Define a LOGMODE that does not specify EXTENDED DATA STREAM or GENERIC. The terminal’s attributes are taken from its LOGMODE PSERVIC definitions.
9. Adjust IOADSNL member

   Adjust the IOADSNL member of the current release to reflect any necessary modifications that were specified in the IOADSNL member of the previously installed version. Take special note of DATASET statements with DSN values that refer to the previously installed version, and correct them accordingly.

10. Adjust IOADFLTL member

    Adjust the IOADFLTL member of the current release to reflect any WISH options that were specified in the IOADFLTL member of the previously installed version. Identify WISH statements that are now configured via standard parameters, and if you find any, remove them and set the corresponding parameters in the relevant product or component configuration.