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.
By installing APAR PI79321, you can run Workload Automation Programming Language without the need of reference files at startup time, and with a JCL that is simpler and more efficient. Therefore, the old procedure EQQYXJCL is deprecated; you can use procedure EQQYXJPX, instead.
- EQQYXTOP
- Use this compiled REXX EXEC in batch or online TSO. It can be called by other REXX EXEC programs
and receive commands through the REXX stack. It can also send data to calling EXEC programs through
the REXX stack. The EQQYXJPX procedure is provided to run EQQYXTOP.
This should be the primary method to run Workload Automation Programming Language.
- EQQWAPL
- Use this load module in batch, or call it from other load modules. Commands are passed through a control block and data is received by a control block. The load module does not create an internal TSO environment, so some commands and options are not available. The EQQYXJPL procedure is provided to run EQQWAPL.
LOADDEF
statement. The following example shows how to send ILSON data to
MYDATA and Batch loader output to the REXX
stack:LOADDEF AD* DATA(MYDATA) LOADER(*)
DD statement | Description |
---|---|
EQQCPOP | Optional. Use this DD statement to identify the occurrence or operation that is
controlling the job in the current plan. This prevents Workload Automation Programming Language from
unnecessary searching in the CP. For example, to identify the jobs that are
submitted by HCL Workload Automation for Z, set
EQQCPOP as follows:
To identify the jobs
that are not submitted by HCL Workload Automation for Z, set the
EQQCPOP to a single hypen
(-):
|
EQQDUMP | Optional. A diagnostic log, which might include additional information about problems. Use
this DD statement if you specified TRACE in EQQYPARM. |
EQQMLIB | Required. The HCL Workload Automation for Z message library, which is normally delivered in the SEQQMSG0 library. |
EQQMLOG | Required. The log for any message issued from HCL Workload Automation for Z. |
EQQOPTS | Optional. Use this DD statement to set the options specific for your environment. It can be
either a sequential file, a member in a partitioned data set, or a library. When you use EQQWAPL as a service within a permanently available started task, do not use EQQOPTS, because if the started task tries to run EQQWAPL in parallel this might produce I/O problems. |
EQQSMTP | Optional. This DD statement is needed only if you are issuing the
SENDMAIL command. Define a SYSOUT DD statement pointing at the SMTP class
and writer, for example //EQQSMTP DD SYSOUT=(B,SMTP) |
EQQYLOGx | Optional. If you define an EQQYLOGx DD statement, all Workload Automation Programming Language messages are directed to this file. x can be a number from 1 to 5, and determines the message level used. For details, see MSGLEVEL – Output message level. |
EQQYPARM | Optional. Use it to provide an override INIT statement, to set
running options. |
OUTBL | Optional. The default output destination for batch loader statements when you use
LOADDEF to load predefined output statements. |
OUTDATA | Optional. The default output destination for ILSON data when you use
LOADDEF to load predefined output statements. |
STEPLIB | Optional. This DD statement is needed when:
|
SYSPROC | Used only for EQQYXTOP. Use this DD statement to point to the library containing the REXX entry point EQQYXTOP. This is normally delivered in the SEQQMISC library |
SYSTSIN | Used only for EQQYXTOP. TSO environment terminal simulated input. Allocate to DUMMY. |
SYSTSPRT | Required (even if you defined an EQQYLOGx DD statement). The main message output stream. |