Home
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.
Customization and Tuning
Customizing HCL Workload Automation for Z
Using the data store
Activating the data store

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

Activating the data store

The data store start JCL can be created by copying the supplied sample, EQQARCH, and customizing it to meet your installations needs with regard to naming convention and the number of files to be used.

The following shows the JCL statements that are typical of the data store, and which do not apply to other HCL Workload Automation for Z components (like the controller or the tracker):

 //OCDST1 JOB CLASS=Y
 //OCDST1 EXEC PGM=EQQFARCH,REGION=0M,PARM='EQQDSTP',TIME=1440
 .
 .
 .
 //EQQSDF01  DD  DISP=SHR,DSN=OPCDEV.SDF01
 //EQQUDF01  DD  DISP=SHR,DSN=OPCDEV.UDF01
 //EQQUDF02  DD  DISP=SHR,DSN=OPCDEV.UDF02
 //EQQPKI01  DD  DISP=SHR,DSN=OPCDEV.PKI01
 //EQQSKI01  DD  DISP=SHR,DSN=OPCDEV.SKI01