Knowing the context of the current plan
To run, many Workload Automation Programming Language processes need to know the application ID, IA date and time, and operation number of the occurrence that is controlling the Workload Automation Programming Language job. When required, Workload Automation Programming Language attempts to find itself in the current plan so that it can perform these processes.
- Access to the supplied variables that reference the occurrence or operation.
- Access to the user fields related to the operation.
- Date calculations that need to know the calendar in use.
- Actions that need to update the operations in the same occurrence (for example, using the = = operator to reference the current application and input arrival).
- Actions that read variables from tables, which need to know the name of the table referred by the occurrence.
If you access any of these functions, Workload Automation Programming Language attempts to find itself in the current plan by searching for an operation in Started status with a job of the same job name and JES number. In big current plans, this can generate large CPU consumption; to prevent the search, you can provide the information in advance.
- For jobs scheduled by HCL Workload Automation for Z
- Set the EQQCPOP DD statement as in the following
example:
//*%OPC SCAN //RUNWAPL EXEC EQQYXJPX,SUBSYS=INDC //EQQCPOP DD * &OADID &OYMD1&OHHMM &OOPNO //SYSIN DD * SHOW OPTIONS
Alternatively, you can use theOPID OPTIONS
keyword in the ARGS symbolic parameter//*%OPC SCAN //RUNWAPL EXEC EQQYXJPX,SUBSYS=INDC, // ARGS=’OPID(&OADID &OYMD1&OHHMM &OOPNO)’ //SYSIN DD * SHOW OPTIONS
- For jobs that are not scheduled by HCL Workload Automation for Z
- To prevent the job trying to locate itself in the current plan, set one of the
following commands:
-
//EQQCPOP DD * -
OPTIONS OPID(-)
-
//*%OPC SCAN //RUNWAPL EXEC EQQYXJPX,SUBSYS=INDC //SYSIN DD * OPTION OPID(-) SHOW OPTIONS
-
EQQCPOP DD
or
OPTIONS OPID
appropriately, you can additionally prevent this
search process.