Almost all CA OPS/MVS TSO command processors have a SUBSYS keyword. Use this keyword to specify the subsystem ID of the copy of CA OPS/MVS on the local system, from where the command was issued, that should process the command.
The only exception is the OPSWAIT command processor. Since execution of OPSWAIT does not require communication with a CA OPS/MVS subsystem, it does not support the SUBSYS keyword.
The CA OPS/MVS default subsystem ID is OPSS. To start an alternate copy of CA OPS/MVS, include the SSID parameter on the z/OS START command and specify the subsystem ID of the CA OPS/MVS copy to be started. To use OPSVIEW with a particular CA OPS/MVS subsystem, you can either specify the SUBSYS keyword on the OPSVIEW command processor or, once in OPSVIEW, change the subsystem ID in option 0.1.
We recommend using OPST as the subsystem ID for your test release of CA OPS/MVS. If you need more SSIDs, then use OPSU, OPSV, OPSW, and so on. z/OS limits subsystem IDs to four characters; CA OPS/MVS requires that the first three characters must be OPS and the fourth character must be alphabetic.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|