CA OPS/MVS runs as a z/OS subsystem. Such subsystems are defined at IPL time through statements in the appropriate IEFSSNxx member of the Logical Parmlib Concatenation. However, in reality, most subsystems are added dynamically.
If CA OPS/MVS is not defined in your IEFSSNxx member, then CA OPS/MVS uses the standard z/OS interface to add its SSCT dynamically. So, whether you update your IEFSSNxx member depends on the policy of your site.
Member IEFSSNOP of the SYS1.OPS.CCLXCNTL data set contains the following example statements that you can insert in your production IEFSSNxx member of the Logical Parmlib Concatenation to define the standard production and test subsystem names for CA OPS/MVS:
OPSB OPSLOG BROWSE ONLY OPS/MVS OPST TEST OPS/MVS OPSS PRODUCTION OPS/MVS
Your production CA OPS/MVS should be listed last, as in the example above. However, if you have another subsystem that must be last, your production CA OPS/MVS should be listed just before that last system.
The parameters SSICMD and SSIMSG affect when CA OPS/MVS processes messages and commands relative to other subsystems.
Copyright © 2014 CA Technologies.
All rights reserved.
|
|