Running Workload Automation Programming Language in batch

With APAR PI79321, the EQQYXJPX JCL procedure is provided to run the complete EXEC version of Workload Automation Programming Language in batch, by loading EQQREF, EQQLANG, and EQQFILE internally and making EQQOPTS optional. To reduce startup I/O processing, use EQQYXJPX instead of the EQQYXJCL procedure for all new Workload Automation Programming Language jobs.

The simplest use of EQQYXJPX is a call to the procedure, with a SYSIN DD statement to enter the commands. The following example shows how to add an application to the plan:

//RUNWAPL  EXEC EQQYXJPX,
//         SUBSYS=WSMC   
//SYSIN    DD *          
ADD ADID(ADHOC)

With EQQYXJPXY, you can use the following symbolic parameters:

ARGS: Additional OPTIONS to be passed to Workload Automation Programming Language. They are run after any statements in EQQOPTS, but before any statements within the REXX stack, passed control block, or SYSIN.
CMD: REXX EXEC entry point to use (default is EQQYXTOP).
To run your own REXX EXEC, call EQQYXTOP and pass the name of your EXEC using the CMD symbolic. Ensure that your EXEC is included in the SYSPROC concatenation.
REG: REGION to allocate (default is 4M).
MOD: The Workload Automation Programming Language Fix Pack level, which indicates a release of Workload Automation Programming Language between GA versions. Specify the Fix Pack level in the format +nnn, for example MOD=’+001’. Unless you need to connect to or generate output for an earlier version of the product, do not set the MOD keyword to any value. The default is the Fix Pack level of Workload Automation Programming Language installed.
SUBSYS: The controller with which to communicate.
VER: The Workload Automation Programming Language version. You can specify the version in various formats, to allow the same symbolic to be used in data set names where appropriate (for example VER=950, VER=V950, VER=V9R5M0). For versions later than 9 and earlier than 16, you can also use the hexadecimal format (for example, VER=A10 for version 10.1).
Unless you need to connect to or generate output for an earlier version of the product, do not set the VER keyword to any value. The default is the version of Workload Automation Programming Language that is installed.

Use the OUTPUT and LOADDEF statements to specify additional DD statements to be used. By default, ILSON data is written to OUTDATA and batch loader data is written to OUTBL, but keywords in LOADDEF overrides original keyword values in the predefined OUTPUT statements.

The following example shows a Workload Automation Programming Language job to send ILSON data to MYDATA DD statement. Because no LOADER keyword is specified, Batch Loader data is sent to the OUTBL DD statement, according to the default behavior.

//RUNWAPL  EXEC EQQYXJPX,              
//         SUBSYS=WSMC                 
//MYDATA   DD SYSOUT=*,LRECL=1024      
//OUTBL    DD SYSOUT=*                 
//SYSIN    DD *                        
OPTIONS STRIP(Y) SHOWDFLT(N) SELECT(Y) 
LOADDEF AD* DATA(MYDATA)               
LIST ADCOM ADID(ADHOC) VALID(=)

Set the ARGS symbolic parameters to specify the OPTIONS keywords rather than including them in SYSIN, as shown in the following example. In this way, the OPTIONS are influenced directly in JCL, rather than within SYSIN data sets.

//RUNWAPL  EXEC EQQYXJPX,                       
//         ARGS='STRIP(Y) SHOWDFLT(N) SELECT(Y)',
//         SUBSYS=WSMC                          
//MYDATA   DD SYSOUT=*,LRECL=1024                
//OUTBL    DD SYSOUT=*                           
//SYSIN    DD *                                 
LOADDEF AD* DATA(MYDATA)                         
LIST ADCOM ADID(ADHOC) VALID(=)

If you reference a supplied variable or user field related to the controlling occurrence in the current plan, Workload Automation Programming Language batch jobs check if they are being controlled within the CP by searching for a started instance of the job name under which they are running, to find an operation with the same JES number. This works if the job is submitted outside of the controller or tracker but tracked in the current plan, or if the job is submitted from the controller or tracker.

For jobs that are submitted by the controller or tracker, you can be more efficient in identifying the controlling occurrence by passing the details directly from the supplied JCL tailoring variables through an EQQCPOP DD statement, as shown in the following example:

//RUNWAPL  EXEC EQQYXJPX,
//         SUBSYS=WSMC   
//SYSIN    DD *          
ADD ADID(ADHOC)   
/*
//*%OPC SCAN 
//EQQCPOP  DD *                  
&OADID. &OYMD1.&OHHMM. &OOPNO

To identify the jobs that are not submitted by HCL Workload Automation for Z and prevent unnecessary searching in the CP, set the EQQCPOP DD statement to a single hyphen (-) as follows:

//EQQCPOP DD *
-

Alternatively, you can set the OPTIONS OPID(-) command.