System Definitions

The IOA subsystem name, as defined in IOA Installation parameter SUBSYS, must be the first subsystem name after the primary subsystem in the subsystem list (member IEFSSNnn in SYS1.PARMLIB). This enables Control‑O to control commands directed to other MVS subsystems before they are executed by these subsystems. However, to control JES commands before they are executed by JES, Control‑O uses JES exits or an additional subsystem name, defined optionally in the Control‑O installation parameters. For more information, see the JCMDSSN parameter in the Control‑O chapter of the INCONTROL for z/OS Installation Guide: Installing.

Note: The subsystem name can be defined by using positional parameter IEFSSNnn or by using the keyword parameter form of the IEFSSNnn PARMLIB member.

When using the keyword parameter form, add a record to member IEFSSNnn in the following format:

SUBSYS SUBNAME(xxxx)

where xxxx is the name of the subsystem specified in IOA installation parameter SSNAME.

For more information, see the IBM manual MVS Initialization and Tuning Reference.

The Control-O monitor must be started at an early stage of IPL. To do this, its procedure and included members should reside in a PROCLIB library specified in member MSTJCLxx in the IEFPDSI DD statement, and a START command should be added to member COMMNDnn in the SYS1.PARMLIB library. To achieve this, do the following:

1. Make sure the IOA environment was installed using the IEFJOBS DD statement.
2. CTOTROLO, IOASETxx, and IOAENVxx procedures must reside in SYS1.PROCLIB or another PROCLIB specified in the MSTJCLxx member in the IEFPDSI DD statement.
3. The JCLLIB from the CTOTROLO procedure in the IOA PROCJCL library referenced by the IEFJOBS DD statement in the MSTJCLxx member should be removed (or commented out).
4. Member COMMNDnn in the SYS1.PARMLIB library (where nn is either the number specified in member IEASYS in the same library, or 00) must contain the following command as one of the first commands in the member:

The following Control‑O and IOA files are allocated to the Control‑O monitor:

• IOA LOAD library
• IOA Global Variables library (dynamically allocated)
• IOA Conditions file
• Calendar library
• PARM library
• Message Statistics file (dynamically allocated)
• Rules library (dynamically allocated)
• Automation Log file (dynamically allocated)

Because Control‑O is started as part of IPL, you must either catalog all these files in the MVS Master Catalog, or specify the VOLSER and UNIT parameters for each of the files. The dynamically allocated files (for example, the Message Statistics file) must be in the Master catalog.

If you specified parameters VOLSER and UNIT for these files and you move the files to another disk, you must modify the Control‑O procedure as well.

Ensure that a correct value is specified for the JESTYPE IOAPARM parameter. Do not leave it blank.

It is recommended that Control‑O start and control the initialization of other system components (JES, VTAM, TSO, and so on).

The on-site enqueue manager must be up before any attempt is made by Control‑O to update any IOA file. For more information, see the QNAME parameter in the IOA chapter, and the CTOQNAM parameter in the Control‑O chapter, of the INCONTROL for z/OS Installation Guide: Installing.