Reporting events to HCL Workload Automation for Z

This chapter describes how you can report events to HCL Workload Automation for Z. This chapter contains General-use Programming Interface and Associated Guidance Information.

HCL Workload Automation for Z lets you track activities in your data processing environment. Information about the status of these activities can be reported manually by dialog users or collected automatically by HCL Workload Automation for Z. These activities are known as events. For z/OS systems, HCL Workload Automation for Z uses SMF and JES exits to collect event information automatically. For example, HCL Workload Automation for Z reports when a started task has started or when a job has ended. But there might be activities in your production workload that cannot be detected by JES and SMF exits, which you want to report to HCL Workload Automation for Z. You can do this by supplying event information to HCL Workload Automation for Z.

For example, assume that an HCL Workload Automation for Z application is dependent on a data set that is updated by an online transaction. For such an application, the batch job that uses the data set must not be started until the data set has been successfully updated. You ensure this by defining a special resource that is needed by the batch job but is unavailable. The online transaction can then make the special resource available by calling the EQQUSIN subroutine or issuing an SRSTAT command as its last processing step. Alternatively, you can define an operation at a general automatic workstation that is set to complete by the online transaction, using EQQUSIN or the OPSTAT command. The batch job, which is dependent on this operation, does not process before the data set has been updated.