An alternate method for controlling VM processing

About this task

Under VM, some EXECs must be run in given sequences, and the results must be checked to ensure that the EXECs have completed successfully. Such work might be repeated at regular intervals. In addition, some applications might require that VM processing interface with, or be synchronized with, z/OS processing.

So, there is a need for VM production control mechanisms that correspond to those that exist under z/OS. Here is one way you can automate control of VM operations:
  1. Set up a z/OS job to send a request to a VM AUTOLOG user to execute an EXEC; you would normally do this using an NJE-RSCS link. On completion, the EXEC sends a job back to z/OS, which issues an OPSTAT command to inform IBM® Z Workload Scheduler of the status of the VM operation. The first z/OS job is scheduled by IBM® Z Workload Scheduler in the same way as any other computer workstation operation.
  2. Set up a second operation to represent the execution of the VM EXEC. You should define the operation on a general workstation with the automatic reporting attribute, which is set up for this purpose. This is the operation whose status is changed by the OPSTAT command issued by VM.

You can use this method to plan, control, and track the workload of multiple VM users at local and remote sites.

This method does not use any IBM® Z Workload Scheduler exits or require other programming effort. The sample library member EQQCVM is maintained for installations that have implemented this method in OPC/A or previous IBM® Z Workload Scheduler releases.