HCL Workload Automation for Z
Welcome to the HCL Workload Automation for Z documentation, where you can find information about how to install, maintain, and use the product.
- Program Directory
- Dynamic Workload Console Readmes
  For the latest information about a Dynamic Workload Console fix pack, see the appropriate Readme File.
- Planning and Installation
- Customization and Tuning
  - About this publication
  - Customizing HCL Workload Automation for Z
    - Defining initialization statements
    - Identifying related initialization-statement parameters
    - Implementing security
      This chapter explains how you use HCL Workload Automation for Z security features to protect HCL Workload Automation for Z functions and data.
    - HCL Workload Automation for Z exits
      Read the following information to understand General-use Programming Interface and Associated Guidance Information. It describes exits that are called by HCL Workload Automation for Z. Your own programs can use the information passed by the exits to perform a variety of functions.
    - Open Systems Integration
    - Reporting Events
    - Using the Job Completion Checker
    - Using the data store
    - Miscellaneous customization
  - Data integrity
  - Tuning
  - HCL Workload Automation for Z macros
  - Sample library (SEQQSAMP)
- Managing the Workload
  You can plan when and how your workload runs and manage it as part of a plan.
- Scheduling End-to-end with z-centric Capabilities
- Quick Reference
- Diagnosis Guide and Reference
- Workload Automation Programming Language for z/OS User's Guide and Reference
- Driving HCL Workload Automation for Z

Structured data files

The structured data files contain job log SYSOUTs in a form based on the parsing of the three components of the job log, the JESJCL, the JESYSMSG and the JESMSGLG, especially the first two. User SYSOUTS are excluded from the structuring mode. Each job log stored consists of two distinct parts:

A number of pages, each consisting of 4096 bytes dedicated to the expanded JCL
A number of pages dedicated to a complete, hierarchically ordered set of structured elements for the restart and cleanup functions.

Therefore, the minimum page number used by a structured SYSOUT is 2, and the medium space usage depends on the job complexity.

To determine the optimal dimension for the structured data files, follow the instructions provided for the allocation of the unstructured data file, but take into account that the user SYSOUTs are not present. For the medium structured SYSOUTs, apply the criteria used for the unstructured job log: the larger memory requirement of the small, structured SYSOUTs, compared to the corresponding unstructured form, is balanced by the larger memory requirement of the unstructured form when the SYSOUT complexity increases.