Using the data store

The role of the HCL Workload Automation for Z data store is to locally store a copy of the SYSOUT data that is produced for submitted jobs. This data is transmitted back to the HCL Workload Automation for Z controller only when requested, that is, only when it is needed for restart and cleanup actions or when explicitly requested for browsing.

In a z/OS® environment the data store must be already installed before you can perform either job log retrieval or restart and cleanup.

The data store automatically cleans itself up at a user-specified frequency according to user-specified criteria, in order not to grow excessively.

When the same operation requires multiple restarts, in order to store only the sysouts needed by restart and cleanup to optimize data access, a component of the data store, called Database, is activated within the controller. As a part of the controller, this component is called local data store. Inside the local data store the internal cleanup operations are synchronized with the Current Plan extension.