Submitting started tasks

This is how HCL Workload Automation for Z submits operations on computer workstations with the STC attribute:
  • The current plan is locked to prevent other tasks or users from updating the operations.
  • The best candidate for submission is chosen as described in Identifying the order of submission.
  • If the operation has been marked with a NOP, HCL Workload Automation for Z immediately sets the operation to complete.
  • HCL Workload Automation for Z attempts to find the STC procedure JCL in the JS file. The JCL will be found here only if a dialog user has updated the JCL or if this operation occurrence has been previously submitted.
  • If the JCL is not found on the JS file, HCL Workload Automation for Z attempts to find it (the member name must be the operation name) in the EQQJBLIB partitioned data set concatenation, first calling the EQQUX002 exit if it is loaded.
  • If no JCL can be found, the operation is given an extended status E to indicate the error; and a message is written to the HCL Workload Automation for Z message log.
  • If the JCL is found, either in the JS or in EQQJBLIB or returned by EQQUX002 exit, JCL substitution is performed, if required, and the job submit user exit is called.
  • A copy of the JCL is written to the JS file. The JCL and workstation destination are queued. The operation status is set to S and extended status U is assigned to indicate that submission is in progress.
  • If there are more operations eligible to start, HCL Workload Automation for Z will move on to the next best candidate, up to 5 operations can be started.
  • The current plan lock is released.
  • The destination is resolved, it can be either a submit/release data set, an XCF link, an NCF link, a TCP/IP link, or blank. If the destination is blank, the JCL is directed to the system the controller is started on.
  • When the JCL arrives at the destination, the procedure JCL is written into the partitioned data set referenced by ddname EQQSTC.
  • HCL Workload Automation for Z then builds and issues the z/OS® START command. Once the command is issued and processed by JES, the procedure JCL is deleted from the EQQSTC data set.
  • The extended status of the operation is set to blank.
  • When HCL Workload Automation for Z learns from JES that the started-task is executing, the extended status is set to S.

If the JTOPTS keyword QUEUELEN is specified, HCL Workload Automation for Z starts up to the number of operations defined by QUEUELEN. For information about the QUEUELEN parameter, see the JTOPTS statement.