Examples of operations

There is no need to restrict operations to those relating to batch processing. If you rely on people remembering to perform a certain task, consider specifying the task as an operation.

The operations in the example for EQQAMOPL - Operations are in the PAYDAILY application for the Paymore system. At the specified time, operation 005 will automatically be set to ready status. When that occurs, the product builds a WTO message and sends the message to the destination specified on the WTO1 workstation definition. The resulting status of the operation depends on the reporting attribute of the workstation. If the workstation reporting attribute is completion-only, the application sets the WTO operation to complete as soon as it is sent, but if the successor operation depends on some action, as in this case, it is better to give the WTO workstation the automatic reporting attribute, so that the product waits for some event (such as an OPSTAT command) to complete the operation.

NetView® can be used to intercept the WTO, issue the appropriate CICS® commands and check for successful deallocation of the online application. When NetView® has determined the online system has successfully shut down, it can execute the EQQEVPGM program specifying this input:

OPSTAT JOBNAME(PAYDAILY) STATUS(C) WSNAME(WTO1)

The EQQEVPGM program creates a job-tracking event that is communicated to HCL Workload Automation for Z by the same means that job start and job end events are. When the controller receives the event, operation 005 is set to completed status, allowing the PAYDAILY job to be submitted.

This process can be very quick, and it ensures that the online application is shut down at the correct time and without delay. It further ensures that the batch processing does not start until the online application has completely shut down.