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
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.
Creating user exits manually
Time-dependent-operation exit (EQQUX014)
Interface to the exit
Limitations

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.
      - User exits invocation
      - Creating user exits through the User Exits Workbench
        As an alternative to creating user exits manually, you can create, edit, compile, and link-edit a number of user exits through the User Exits Workbench tool. The tool enables you to customize your user exits by using the IBM z/OS Metal C language (for details about this language, see the IBM z/OS Metal C Programming Guide and Reference).
      - Creating user exits manually
        HCL Workload Automation for Z Start/Stop exit (EQQUX000)
        Job-submit exit (EQQUX001)
        Job-library-read exit (EQQUX002)
        Application-description-feedback exit (EQQUX003)
        Event-filtering exit (EQQUX004)
        SYSOUT archiving exit (EQQUX005)
        Incident-record-create exit (EQQUX006)
        Operation-status-change exit (EQQUX007)
        Operation-initiation exit (EQQUX009)
        Job-tracking log write exit (EQQUX011)
        Job-tailoring event exit (EQQUX013)
        Time-dependent-operation exit (EQQUX014)
        Installing the exit
        Interface to the exit
        Example
        Limitations
        EQQDELDS/EQQCLEAN Catalog exit (EQQUXCAT)
        EQQCLEAN GDG Resolution exit (EQQUXGDG)
        JCL-imbed exit
        Variable-substitution exit (on JCL or job definition variable)
        Automatic-job-recovery exit
        Daily-planning-report exit (EQQDPUE1)
        Application-description-validation exit (EQQUXPIF)
        System Automation for z/OS® user exit (EQQUXSAZ)
    - 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

Limitations

The controller uses the returned TOFFS value to update the job start time and leaves unchanged the latest start time. This might affect latest start time-related activities such as:

The processing of the SUPPRESS IF LATE option.
Alert conditions or critical jobs monitoring. For example, consider a job with 9:00 as start time and 9:30 as latest start time. Supposing that the exit returns +0060 as TOFFS, the job becomes late as soon as it is ready to start.