Submitting and tracking the workload

Managing the Workload contains details of how Tivoli Workload Scheduler for z/OS selects work to be submitted at particular workstations. The following is a summary of the submission and tracking process for operations on a workstation that has a user-defined destination ID:

• When the operation is selected as the next operation to be submitted, the status is set to SU. Tivoli Workload Scheduler for z/OS calls EQQUX009 and provides data stored in the EQQJSxDS or EQQJBLIB datasets. The information does not have to be stored in these libraries; the exit could locate the data elsewhere or the data might be stored at the target destination.
• EQQUX009 transmits the data to the target destination. A good return code from the exit will leave the operation in status SU until changed through either the normal Tivoli Workload Scheduler for z/OS tracking routines (if the job is run on z/OS and an event writer and an event data set are present) or through the OPSTAT interface.
• If the operation enters a queuing system in the target destination, this can be reported to Tivoli Workload Scheduler for z/OS through the OPSTAT command with STATUS(Q). Tivoli Workload Scheduler for z/OS will set the operation status to SQ.
• When the operation actually starts to execute, this is reported using the OPSTAT command for STATUS(T). Tivoli Workload Scheduler for z/OS will set the operation status to SS.
• Termination is reported using the OPSTAT command for STATUS(C), if normal, or STATUS(E), if abnormal.

It is recommended that you use the TOKEN passed to the EQQUX009 as input to OPSTAT. The TOKEN is a 4-byte value automatically generated by Tivoli Workload Scheduler for z/OS when the operation is selected to be scheduled. The purpose of the token is to make it easier for OPSTAT users to uniquely identify a Tivoli Workload Scheduler for z/OS operation.