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.
Contains the information that you need to initialize CA OPS/MVS.
Incompatible levels could be a problem. Contact CA Support.
Limits concurrent z/OS commands. If you have no subsystem extended consoles, OPSCMD, OPSRMT, and OPSVIEW will not function.
Default: 2
Number of extended consoles without MIGIDs.
Default: 8
Recommended: 8
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
For information to help you calculate how much DASD space you will need to install and run CA OPS/MVS, see the Administration Guide.
You do not need to catalog data sets in your z/OS master catalog.
Has to be STEPLIB, LINKLST, or LPALIB. Installation usually goes faster using the STEPLIB method.
Can circumvent need for IPL by copying to LINKLST library, or by dynamically authorizing SYS1.OPS.CCLXLOAD.
Required only to execute CA OPS/MVS TSO commands (for example, OPSCMD) when the product is down.
The subsystem ID (that is, OPSS) is inserted dynamically if not in the parmlib library.
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.
Same as above.
Could be a problem. Contact CA Support.
Required.
Copyright © 2014 CA Technologies.
All rights reserved.
|
|