Setting up the Workload Automation Programming Language environment

If you run a version of SOE or Workload Automation Programming Language JCL that refers to SEQQWAPL members without the EQQ prefix, ensure that you set up the environment by running the EQQWPLCO sample job.

Note:
  1. When you run Workload Automation Programming Language jobs under the control of current plan, to enable the use of Workload Automation Programming Language occurrence variables, or of the == short form, ensure that you run the WAPL job with a user ID that has read access to the CP occurrence or operation controlling the job. Otherwise, a message similar to the following might be issued: 
    EQQI012A Job ZUSRDH1W,JOB02218 is external to IWS
  2. To use Operation User fields to contain Workload Automation Programming Language commands, ensure that you run the job with a user ID that has read access to the CP occurrence or operation controlling the job, and read access to the user fields containing the commands. Otherwise, a message similar to the following might be issued: 
    EQQI145E No user fields match EQQ-SYN-*
  3. To ensure accurate use of queries for input arrival, set CWBASE (century window base) and HIGHDATE to 00 and 711231, respectively (these are the default values). If CWBASE and HIGHDATE are set to values different than the defaults, any queries against input arrival fields fail. If the EQQCPOP DD statement is used together with the supplied variable &OYMD1, Workload Automation Programming Language cannot locate itself in the current plan, message EQQI012A is issued, and the supplied occurrence variables or user fields are not accessed.

    For details about the settings of CWBASE and HIGHDATE in the INIT statement, see INIT.

  4. When you use Workload Automation Programming Language, do not set DATINT to YES in the INIT statement of EQQYPARM. This setting would create a lock conflict when performing OPTIONS DBMODE(UPDATE) or OPTIONS DBMODE(COPY), and data could get lost.