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.
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.

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.
    - 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.
      - JBSTART – Application details
        The JBSTART statement describes the application level information, based on the ADSTART statement and using all the same keywords, except for ADID. ADID is ignored and replaced with a name formed by PFX, the job name, and SFX.
      - JBCIV and JBXIV – External dependency selection criteria
        These are generated by LISTJOB for information purposes only. Dependency selection criteria is handled by the CRITERIA, DEPTIME, INTLINK, and EXTLINK keywords of the JBSTART statement. They are ignored when the JBSTART command is run.
      - JBCNC and JBCNS – Conditional dependencies
        These are generated by LISTJOB for information purposes only. JBSTART is used to dynamically submit jobs on demand, therefore the decision as whether the job is to be run must be made before running the JBSTART statement. They are ignored when the JBSTART command is run.
      - JBDEP, JBPRE and JBSUC – Dependencies
        JBDEP is not a supported statement for JBSTART, because JBSTART allows dependencies in both directions. JBDEP is replaced by JBPRE to define predecessors and by JBSUC to define successors.
      - JBRUN and JBRULE - Run cycle and rule
        LISTJOB does not generate a JBRUN or JBRULE statement, because it only lists application level information, then the complete specification of the job with the JBOP statement and statements for any child segments of the operation being listed.
    - 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

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.

The LISTJOB command extracts application and job details from the database for a single job, but can be made to output this detail in the form of a JBSTART command. So where the ADDJOB command will extract job details and then submit the job directly to the plan with the extracted attributes, by using LISTJOB to create the JBSTART command this allows you to manipulate the extracted attributes before submitting the job to the current plan.

For example, issue the following LISTJOB command:

LISTJOB JOB005 ADID(ALTIF) OUTPUT(OUTDATA) STYLE(LOADER) DISPLAY(N) 
                  DETAIL(SUCC)

to create the following JB command:

JBSTART ADID(ALTIF) ADVALFROM(141202) DESCR('ALTIF test') OWNER(TWS)  
JBOP WSID(CPU1) OPNO(005) JOBN(JOB005) DURATION(1)                    
JBPRE-INT WSLCCMD1 PREADID(ALTIF) PREWSID(CMD1) PREOPNO(001)          
JBSUC-INT JOB010 SUCADID(ALTIF) SUCWSID(CPU1) SUCOPNO(010)

The JB batch loader statements are similar to the equivalent AD statements, with the difference that the AD prefix is replaced with JB. For a complete description of the AD syntax, see AD – Application definition record.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.