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.
Workload Automation Programming Language for z/OS User's Guide and Reference
Batch loader commands
The batch loader function of Workload Automation Programming Language uses a set of statements to define or modify objects within the HCL Workload Automation for Z database.
Batch loader syntax enhancements
By default, Workload Automation Programming Language supports the same format of batch loader supported by EQQYLTOP. However, the following syntax enhancements make the batch loader function easier to use.
SETDEFAULT behaviour in Workload Automation Programming Language
An element of the EQQYLTOP syntax that is not compatible with Workload Automation Programming Language is the ability to SETDEFAULT for a segment without first providing a SETDEFAULT for the record itself.

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
- 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
  - About this publication
  - Overview
    The Workload Automation Programming Language is a programming language that provides you with easy access to the features of the HCL Workload Automation for Z Program Interface (PIF).
  - Running Workload Automation Programming Language
    You can run Workload Automation Programming Language as a batch job by using the compiled REXX exec, as a load module, online within a TSO session, as a started task workstation, or as a console command. A user program must run as an authorized program.
  - Core programming commands
    The following sections describe the Workload Automation Programming Language commands that control the behavior and logic of the program. Use the commands to set options, return codes, determine an output, modify the flow, change variables, or make decisions.
  - Workload Automation Programming Language functions
    Some commands in Workload Automation Programming Language operate in REXX mode. These commands are CONSOLE, DISPLAY, DO, IF, LOG, SETVAR when the equal sign (=) is used, and WRITE.
  - Data Access commands based on PIF
    The Data Access commands supported by Workload Automation Programming Language are low level commands based on the HCL Workload Automation for Z programming interface (PIF).
  - Current Plan Operation commands
    Use the Current Plan Operation commands to perform specific functions against operations in the current plan, using a common set of keywords to identify the operation you want.
  - Current Plan Occurrence commands
    Use the Current Plan Occurrence commands to perform specific functions against all operations within a single occurrence in the current plan, using a common set of keywords to identify the occurrence.
  - Function Based commands
    The Function Based commands combine various low level PIF commands. Use the Function Based commands to perform specific scheduling or operational functions.
  - Using TSO commands within Workload Automation Programming Language
    Some TSO commands are specific to HCL Workload Automation for Z; you can run them natively in TSO, through program EQQEVPGM, and through Workload Automation Programming Language.
  - Batch loader commands
    The batch loader function of Workload Automation Programming Language uses a set of statements to define or modify objects within the HCL Workload Automation for Z database.
    - Modes of operation
      The batch loader processing supports several modes of operation, which you can specify by setting either OPTIONS DBMODE or the ACTION keyword of individual batch loader statements. Behaviors are different at the different levels.
    - Output masking
      Use output masking to update the content of existing fields using the percent sign (%) and asterisk (* ).
    - Batch loader syntax enhancements
      By default, Workload Automation Programming Language supports the same format of batch loader supported by EQQYLTOP. However, the following syntax enhancements make the batch loader function easier to use.
      - SETDEFAULT behaviour in Workload Automation Programming Language
        An element of the EQQYLTOP syntax that is not compatible with Workload Automation Programming Language is the ability to SETDEFAULT for a segment without first providing a SETDEFAULT for the record itself.
      - Keyword abbreviation
        In Workload Automation Programming Language, you must specify all keywords completely, they cannot be abbreviated. This allows optimum performance for the Workload Automation Programming Language parsing engine. However, the EXTENDED syntax shortens many of the longer EQQYLTOP keywords.
      - Suffixing
        Some Batch Loader statements support the SUFFIX keyword. This allows a variable value to be suffixed onto the name of the object.
      - NEW_ keywords
        With OPTIONS DBMODE(UPDATE) you can change the "name" of an object, by modifying its key fields. In the same way, with OPTION DBMODE(COPY) new key fields must be specified to save a copy to. To do this, the key fields of any HCL Workload Automation for Z object can have alternate names specified by using a NEW_ prefix for any of the key fields you wish to alter.
    - AD – Application definition record
      The AD record is a multi segment record with the following structure.
    - AWSCL – All Workstations Closed record
      The AWSCL record is a single segment record with the following structure.
    - CL – Calendar record
      The CL record is a multi segment record, with the following structure.
    - ETT – Event Trigger Record
      The ETT record is a single segment structure.
    - JB – Ad-hoc in the current plan
      The JB Batch Loader statements do not map to a record within HCL Workload Automation for Z, instead this is pseudo batch loader generated as output from the LISTJOB command.
    - JCLV – JCL Variable Table record
      The JCLV record is a multi segment record, with the following structure.
    - JS – Current Plan JCL record
      The JS record is a multi segment record, with the following structure.
    - OI – Operator Instruction record
      The OI record is a multi segment record, with the following structure.
    - PR – Period record
      The PR record is a multi segment record, with the following structure.
    - RG – Run cycle group record
      The RG record is a multi segment record, with the following structure.
    - SR – Special Resource record
      The SR record is a multi segment record, with the following structure.
    - WS – Workstation record
      The WS record is a multi segment record with the following structure.
    - WSV – Virtual Workstation destination record
      The WSV record is a multi segment record, with the following structure.
  - Variable substitution
    Workload Automation Programming Language supports variable substitution within its control statements. In this way, the actual values required for each command run are provided (for example, the occurrence name or Input Arrival date).
  - Performance considerations
    With Workload Automation Programming Language you can use different methods to perform the same action. Each method has different implications for ease of use and performance, the balance of which might change depending on the volume of records to which it is being directed.
  - Resource reference
  - OPTIONS keywords
    Use the following keywords with the OPTIONS statement.
  - Workload Automation Programming Language variables
    In addition to the HCL Workload Automation for Z variables and user variables, Workload Automation Programming Language has access to some additional information relating to the job running Workload Automation Programming Language and when scheduled the operation and occurrence within which it is running.
  - WAPLEXEC programs
    The Workload Automation Programming Language for z/OS is a REXX based tool provided to give you easy access to the features of the HCL Workload Automation for Z Program Interface (PIF). Workload Automation Programming Language can be extended by WAPLEXEC programs, which are REXX programs using Workload Automation Programming Language functions to tackle specific tasks or functions.
  - Messages and Return Codes
    Messages and return codes provide information for problems occurred.
- Driving HCL Workload Automation for Z

SETDEFAULT behaviour in Workload Automation Programming Language

An element of the EQQYLTOP syntax that is not compatible with Workload Automation Programming Language is the ability to SETDEFAULT for a segment without first providing a SETDEFAULT for the record itself.

For example, in EQQYLTOP the following commands set the default workstation to CPU1 and use that default value in the remaining statements:

ADOP ACTION(SETDEFAULT) DURATION(10)
ADSTART ADID(NEWAPPL)
ADOP WSID(CPU1) OPNO(001) JOBN(JOB1)
ADOP WSID(CPU1) OPNO(002) JOBN(JOB2)

Because Workload Automation Programming Language uses object based structures throughout the syntax, to do the same thing you need to add an ADSTART statement before the ADOP statement to ensure that the structures are coherent:

ADSTART ACTION(SETDEFAULT)
ADOP ACTION(SETDEFAULT) DURATION(10)
ADSTART ADID(NEWAPPL)
ADOP WSID(CPU1) OPNO(001) JOBN(JOB1)
ADOP WSID(CPU1) OPNO(002) JOBN(JOB2)

Note: All the statements within a SETDEFAULT structure can specify only the SETDEFAULT ACTION. If ACTION is not specified for child batch loader statements, SETDEFAULT is assumed.