To issue product commands from the CA VM:Operator SYSTEM window add the appropriate PRODUCT record to the VMOPER CONFIG file:
PRODUCT product-name userid
  • product-name
    Denotes VMACCOUNT, VMARCHIVER, VMBACKUP, VMBATCH, VMDIRECTOR, VMOPERATOR, VMSCHEDULE, VMSECURE, VMSPOOL, or VMTAPE.
  • userid
    Specifies the user ID of the service virtual machine running the corresponding product.

The PRODUCT record identifies which service virtual machine CA VM:Operator is communicating with when invoking a product command. The commands can be invoked from the SYSTEM window command line. The product command actually invokes a CA VM:Operator macro (included with the CA VM:Operator program material) that communicates with the other product.

In addition to the PRODUCT record, add authorizations to the configuration file of each product that you want the user ID running CA VM:Operator to communicate with. For example, to give the user ID running CA VM:Operator privileges to issue CA VM:Schedule operator commands, add this record to the VMSCHED CONFIG file where user ID is the user ID running CA VM:Operator:

AUTHORIZ OPERATOR userid

Product server commands issued from EXECs should (where possible) be issued using CP SMSG. An EXEC attempting to issue a product server command using the communication modules (drones) may produce unpredictable results.

The CA VM:Operator macros included on the distribution tape can be used as prototypes when converting your EXECs to CA VM:Operator macros. When issuing product commands from CA VM:Operator macros, use the CMSNOLCK primitive and the TEST primitive prefix. To do this, preface the call with TEST CMSNOLCK. For example:

'TEST CMSNOLCK VMTAPE QUERY MOUNT'

Restrictions

CA VM:Operator will use product communication modules to issue other product commands instead of using its internal product-to-product interface. This adds greater flexibility to commands that can be issued from the SYSTEM window, but there are still these restrictions:

  • When CA VM:Operator issues a command to a product, CA VM:Operator cannot issue another command to that same product until the first one finishes executing. For example, if a VMYIAMOP user is currently viewing a CA VM:Schedule screen, no other VMYIAMOP user or logon console can issue a CA VM:Schedule command until the first VMYIAMOP user leaves the CA VM:Schedule screens.
  • The CA VM:Spool command must be issued from the LOGON console and must be the only product command active at a given time. For example, if a CA VM:Batch command is executing on a VMYIAMOP console, then a CA VM:Spool command issued on the logon console will not be executed. Conversely, if a CA VM:Spool command is executing on the logon console, a CA VM:Batch command issued on a VMYIAMOP console will be rejected.