Operations › How to Start the Product › Specify the Subsystem to Run the Product

Specify the Subsystem to Run the Product

The subsystem that CA OPS/MVS runs under depends upon the value you specify for the SUB keyword of the z/OS START command.

Typically, you should run CA OPS/MVS under the master subsystem for the following reasons:

• Availability

  As a subsystem of the master subsystem, CA OPS/MVS starts before JES. This means that you can start CA OPS/MVS earlier in the IPL process, and you can use CA OPS/MVS to help to bring up the JES subsystem.

• Reliability

  When CA OPS/MVS runs under the master subsystem, it is insulated from JES problems.

Note: Even if the CA OPS/MVS subsystem ID is defined in the appropriate IEFSSNnn member of the Logical Parmlib Concatenation, CA OPS/MVS will not be automatically started under the master subsystem.

To make sure that the OPSMAIN, OPSOSF, and OPSECF address spaces run under the master subsystem, you must specify SUB=MSTR on the z/OS START command for CA OPS/MVS.

The following shows variations of the z/OS START command:

• To start CA OPS/MVS under the master subsystem, issue the following command:

  START OPSMAIN,SUB=MSTR
  

• To start CA OPS/MVS under JES, issue any of the following commands:

  START OPSMAIN
  OC S OPSMAIN
  OC C(S OPSMAIN)
  OPSCMD S OPSMAIN
  

Note: You must specify SUB=MSTR if CA OPS/MVS runs on the JES3 LOCAL system, because the JCL conversion runs on the JES3 GLOBAL system.