HCL Workload Automation, Version 9.4

Checking JES jobs

To check a JES job that was not launched by HCL Workload Automation, the name of the job is passed by HCL Workload Automation to the gateway. Because HCL Workload Automation did not submit the job, the JES job ID is not available. The Gateway enters the name in the Tablespace, and waits for information about the job to appear in SMF records passed through the IEFU84 exit.

The IEFU84 exit cannot handle every job without impacting the performance of the entire system because it is invoked for each job running on the z/OS system.

If the job is not present in the gateway dataspace, the IEFU84 exit does not perform any action.
If the job is submitted by HCL Workload Automation, the gateway inserts the job into the dataspace. In this case the IEFU84 exit monitors the status of the job and of each step contained in the job.
If the job is not submitted by HCL Workload Automation, the gateway inserts the job into the dataspace only if the gateway receives a request from HCL Workload Automation to check its status because the job represents an internetwork dependency.

To have the internetwork dependencies of a z/OS job correctly handled by IBM Workload Scheduler for z/OS system, ensure that there are no occurrences of the z/OS job in any job queue including the output queue. If any occurrences of the z/OS job are present then purge them. The internetwork dependencies of a z/OS job are handled by HCL Workload Automation in the following ways:

If there are no occurrences of z/OS jobs in the job queues, the gateway inserts the job into the dataspace the first time it receives the request from HCL Workload Automation to check the job status. The gateway inserts the job into the dataspace with an unknown job ID ready to be monitored.
When the z/OS job is submitted, the IEFU84 exit finds the job in the dataspace and updates the corresponding entry with the JES job ID. From now on the z/OS job is monitored using the associated JES job ID. If the job completes successfully, the gateway returns the information to HCL Workload Automation, and the internetwork dependency is correctly resolved.