Starting Your Product › Summary of System Preparation Tasks

Summary of System Preparation Tasks

The following list summarizes the system preparation tasks for CA OPS/MVS. Review it to see the impact of each item on CA OPS/MVS operation.

• CA LMP Key Certificate

  Contains the information that you need to initialize CA OPS/MVS.

• Compatible software levels

  Incompatible levels could be a problem. Contact CA Support.

• z/OS subsystem consoles

  Limits concurrent z/OS commands. If you have no subsystem extended consoles, OPSCMD, OPSRMT, and OPSVIEW will not function.

  Default: 2

• Extended consoles

  Number of extended consoles without MIGIDs.

  Default: 8

  Recommended: 8

• Enough ECSA available

  Could be a problem if you do not have enough available ECSA. Circumvent or reduce by putting SYS1.OPS.CCLXLOAD into LPA/ELPA.

  Recommended: 500 KB

• DASD space for program libraries, OPSLOG Browse messages, and global variables

  For information to help you calculate how much DASD space you will need to install and run CA OPS/MVS, see the Administration Guide.

• Data set naming standards

  You do not need to catalog data sets in your z/OS master catalog.

• Access to CA OPS/MVS load modules

  Has to be STEPLIB, LINKLST, or LPALIB. Installation usually goes faster using the STEPLIB method.

• APF authorize load library

  Can circumvent need for IPL by copying to LINKLST library, or by dynamically authorizing SYS1.OPS.CCLXLOAD.

• TSO command authorization

  Required only to execute CA OPS/MVS TSO commands (for example, OPSCMD) when the product is down.

• Security user IDs for OPSMAIN, OPSECF, OPSOSF, and OPSUSS, and data set access if you have a security system, you need them.
• Provide TSO OPER authority to user IDs.
• This authority must be provided to all user IDs that issue z/OS commands from ADDRESS OPER, OVEVIEW 6, or OPSVIEW 1 panels, run the OPSIVP OPS/REXX program, and so on.
• CA ACF2 command limiting list
• If you run CA ACF2 and you use a command limiting list, OPSVIEW will not work unless its subsidiary commands are included.
• Subsystem ID

  The subsystem ID (that is, OPSS) is inserted dynamically if not in the parmlib library.

• VTAM definitions for the MSF optional component

  Required for the MSF, although the rest of CA OPS/MVS does not need them. The definitions can be added without recycling VTAM if you use separate members.

• VTAM definitions for the EPI optional component

  Same as above.

• IMS AOI exit use of the UEHURSVD field

  Could be a problem. Contact CA Support.

• CCS for z/OS installed

  Required.