HCL Workload Automation, Version 9.4

Defining jobs for end-to-end scheduling

Extended agents
Extended agent jobs scheduled to run in an end-to-end environment cannot be defined using the Dynamic Workload Console or the HCL Workload Automation command line, but must be added to the SCRIPTLIB of IBM Workload Scheduler for z/OS.
In the OPERATIONS ISPF panel of IBM Workload Scheduler for z/OS, extended agent jobs are defined like any other job, but with the specific attribute for a job defined on an extended agent workstation. The following example shows the definition of a job named SAPJOB. This is the IBM Workload Scheduler for z/OS job that drives the running of on SAP R/3 job (named BAPRINT46B as shown in the next example). It shows as an extended agent job because the associated workstation is an extended agent workstation named R3XA.
Figure 1. Defining an Extended Agent job for end-to-end scheduling
--------------------------------- OPERATIONS -----------------Row 1 to 1 of 1 
Command ===>                                                  Scroll ===> PAGE 
Enter/Change data in the rows, and/or enter any of the following               
row commands:                                                                  
I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - Delete                       
S - Select operation details, J - Edit JCL                                     
Enter the TEXT command above to include operation text in this list, or,       
enter the GRAPH command to view the list graphically.                          
Application            : APLL1            FTW appl                             
Row  Oper      Duration  Job name  Internal predecessors           Morepreds   
cmd  ws   no.  HH.MM.SS                                            -IntExt-    
'''' R3XA 001  00.00.01  SAPJOB___  ___ ___ ___ ___ ___ ___ ___ ___   0  0      
******************************* Bottom of data ********************************
For each job, create a member in the SCRIPTLIB of IBM Workload Scheduler for z/OS with details about the job in a JOBREC statement. A SAPJOB member was created for the job of the previous example. It contains a JOBREC statement like this:
   JOBCMD('/-job BAPRINT46B -user MAESTRO -i 14160001 -c C')       
The string in JOBCMD is read and interpreted by the access method before running the job. The job of this example, BAPRINT46B, was previously defined on SAP R/3 and assigned with an ID of 14160001, that was manually written in JOBCMD.
The following example is for a PeopleSoft job. The entire string that follows the JOBCMD keyword must be enclosed within quotation marks ("), because for PeopleSoft jobs single quotes are already used in the string.
   JOBCMD("/ -process XRFWIN -type 'SQR Report' -runcontrol IWS")
IBM Workload Scheduler for z/OS agents
For information about the jobs definition for agent with z-centric capabilities, see Scheduling End-to-end with z-centric capabilities.