Using TSO commands within Workload Automation Programming Language

Some TSO commands are specific to IBM® Z Workload Scheduler; you can run them natively in TSO, through program EQQEVPGM, and through Workload Automation Programming Language.

Within Workload Automation Programming Language, you specify IBM® Z Workload Scheduler TSO commands almost in the same way as the normal IBM® Z Workload Scheduler TSO command with the same name. The only difference is that you are not required to specify SUBSYS.

If you omit SUBSYS from the command, Workload Automation Programming Language adds it by using the information that you set in OPTIONS TRACKERS, to set the correct tracker subsystem name for the controller with which you are communicating. If you did not specify any OPTIONS TRACKERS, the SUBSYS value that was passed to Workload Automation Programming Language at startup is used.

The SUBSYS keyword cannot be abbreviated within Workload Automation Programming Language.

Note:
  • IBM® Z Workload Scheduler TSO commands are asynchronous: they generate an event to perform the action. Successful completion of the command indicates only that the event was generated, it does not mean that the event reached the target or that the keywords identified an object with the correct state for update.
  • With the EQQWAPL load module, you cannot use the TSO commands BULKDISC, DEFINE, DELETE, JSUACT, and REPRO.

For detailed documentation and syntax about TSO commands, see IBM® Z Workload Scheduler: Managing the Workload.