|
|
|
|
|
A. Catalog Control‑O operations files and procedures Yes__ No__ Catalog Control‑O procedures and IOASET to site PROCLIB Yes__No__ B. Data set name (DSN) prefixes, volumes, and units Library Type DSN Prefix Volume Unit Installation ILPREFO ILVOLO ILUNITO Operations OLPREFO OLVOLO OLUNITO |
A. Catalog Control‑O operations files and procedures If Control‑O starts before CATALOG is active (e.g., to start JES), catalog the following Control‑O data sets in the master catalog, prefixed with OLPREFO:
Copy Control‑O procedures in site PROCLIB Copy the Control‑O procedure (CONTROLO) and the Control‑O SERVER procedure (CTOSRV) into a proclib that is available during IPL and before JES is active. You must copy the IOASET to the same library, because JCL resolution (before JES is active) requires it. Major step 5, "Customization Process" Minor step 2, "Copy Several Procedures to Site Library" |
B. Data set name (DSN) prefixes, volumes, and units
|
B. Data set name (DSN) prefixes, volumes, and units Minor step 4.4 "Install Control‑O Libraries" allocates all library prefixes. After prefixes are allocated, they can be modified as soon as the previous data sets are deleted and the libraries are restored. Examples of data set prefixes:
|
C. Disk space requirements Number of Automation log records: ______ |
C. Disk space requirements See Control-O data sets for the disk space requirements for the Control‑O Operations and Installation libraries. Control‑O operating files include the Statistics file, the Global Variables library, and the Automation Log file. The Statistics file and the Global Variables library are relatively small and generally do not cause allocation problems. To estimate the disk space required for the Automation Log file, use the value of the ALREC# installation parameter described in minor step 3.2 "Control‑O Data sets." |
D. Control‑O security requirements Operator command Yes ___ No ___ Library Type Access Type User Category Installation Read 2,3 Yes ___ No ___ Installation Update 1 Yes ___ No ___ Operations Update 1,2,3 Yes ___ No ___ Repository Update 1,2,3 Yes ___ No ___ Legend:
The Control‑O monitor requires:
|
D. Control‑O security requirements The Control-O monitor requires:
|
E. Update SYS1.PARMLIB ___ Protection for Control‑O areas: SCHED ________ ___ Control-O subsystem IEFSSN ________ |
E. Update SYS1.PARMLIB Protection for Control‑O areas: Define the Control‑O program in the SCHEDnn member with the required protection key. See minor step 7.3 "Update Member SCHEDnn in SYS1.PARMLIB" for details. Control‑O subsystem: The Control‑O subsystem name is taken from the SSNAME IOA installation parameter. See Defining subsystems for details about defining subsystems. |
F. Console definitions Number of subsystem consoles (recommended value is 0): ______ Names and number of extended MCS console definitions: system ___ prefix ____ EMCS ___ EMCS+MIGID _____ system ___ prefix ____ EMCS ___ EMCS+MIGID _____ system ___ prefix ____ EMCS ___ EMCS+MIGID _____ system ___ prefix ____ EMCS ___ EMCS+MIGID _____ system ___ prefix ____ EMCS ___ EMCS+MIGID _____ system ___ prefix ____ EMCS ___ EMCS+MIGID _____ |
F. Console definitions Control‑O uses logical consoles to process command responses. A logical console is a console that is reserved for use by special subsystems or a virtual console created and managed by Control-O. Number of subsystem consoles is described under the NUMCONS parameter in minor step 2.1 "Control‑O Operational Parameters." Names and number of extended MCS consoles for each system is described in minor step 2.3 "Define EMCS Consoles." |
G. Control‑O servers Immediate servers number (SRVIMD#): _____________ General servers number (SRVGEN#): _______________ Dedicated servers:
|
G. Control‑O servers Required for DO TSO, DO KSL, and DO SHELL Major step 2 "Specify Control‑O Parameters" Minor step 1 "Control‑O Operational Parameters" Minor step 2 "Define Special Servers " |
H. Install KOA Yes ___ No ___ |
H. Install KOA Review the installation requirements for this optional interface to determine whether special handling is required by you or by other teams in the organization. IOA Major step 22 "Install KOA and IOA Routes (optional)" |
I. Control‑M support Yes ___ No ___ |
I. Control‑M support If Control‑M is installed, you must first execute Control‑M installation step 7, "Install Event Manager (CMEM) / Control‑O Interface". |
J. Install CICS and/or IMS support CICS ____ IMS ____ |
J. Install CICS and/or IMS support These are optional steps. If you do not install CICS support, you will not be able to handle internal CICS messages sent to Transient Data Queues. If you do not install IMS support, you will not be able to handle internal IMS messages sent to the Master Terminal (MTO). |
K. Communication support Yes _____ No _____
|
K. Communication support Major step 11 "Control‑O Communication" The IOAGATE definition requires the name of LU 6.2, which will be the system name of each member of the Control‑O communication group Requires modification in Control‑O rules list. Requires definition of IOAGATE MAP refer to IOA Major step 20 "Install IOAGATE" The IOAGATE map can be TCP/IP or VTAM lu6.2 |
L. COSMOS support Yes _____ No _____ Database definitions in IOAVAR Yes _____ No _____ Global variables database list Yes _____ No _____ Rules list Yes _____ No _____ COSMOS database list Yes _____ No _____ |
L. COSMOS support Major step 10 "COSMOS Customization" Requires modification in IOAVAR database Control‑O global pools' list Control‑O rules list |
M. JES2 support ___ None ___ Exit using the IEFJFRQ subsystem exit ___ Subsystem using Control‑O (not recommended) JES2 command suppression subsystem name: ______________ |
M. JES2 support If you skip the JES2 support step, you will not be able to modify or suppress JES2 commands. See the JCMDSSN parameter in minor step 2.1 "Control‑O Operational Parameters." |
N. OMEGAMON support Yes _____ No _____ |
N. OMEGAMON support Major step 12 "OMEGAMON Support" May requires changes in the OMEGAMON monitor STCs Requires the definition of the Control‑O subsystem in the CTOPARM ALTSSN |
O. SMS support Yes _____ No _____ Note: IPL with CLPA is required to activated the SMS support |
O. SMS support Copy the IGDACSD, IGDACSM, IGDACSS modules to site LPALIB Major step 7 "Adjustments" Minor step 4 "ON SMS support of Control‑O" |
P. SYSOUT data capture ___ None ___ Using the IEFJFRQ subsystem exit |
P. SYSOUT data capture |
Parent Topic |