Defining fault-tolerant workstation jobs

The jobs scheduled to run in an end-to-end environment must be added to the SCRIPTLIB, and optionally in the JOBLIB, of IBM Z Workload Scheduler.

In the OPERATIONS ISPF dialog of IBM Z Workload Scheduler, the end-to-end jobs are defined like all other operations, but the choice of a fault-tolerant workstation denotes their kind. The following example shows the definition of a job named SAPJOB. This is the IBM Z Workload Scheduler job that is to drive the run of an 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 a 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, a member must be created in the SCRIPTLIB of IBM Z Workload Scheduler 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:
 JOBREC                                            
   JOBCMD('/-job BAPRINT46B -user MAESTRO -i 14160001 -c C')
   JOBUSR(twsila)                           

The string in JOBCMD is read and interpreted by the access method prior to running the job. The job of this example, BAPRINT46B, was previously defined on R/3 and assigned with an ID of 14160001, that was manually transcribed in JOBCMD.

The following example is for a PeopleSoft job. The entire string that follows the JOBCMD keyword must be enclosed in double quotation marks rather than single quotation marks, because single quotation marks are already used in the string.
JOBREC
   JOBCMD("/-process XRFWIN -type 'SQR Report' -runcontrol TWS")
   JOBUSR(PsBuild)
The following example is for a Tivoli® Dynamic Workload Broker job. When you define a job that is to run in a Tivoli® Dynamic Workload Broker system, the argument of the JOBCMD keyword is simply the name of the Tivoli® Dynamic Workload Broker job (properly defined in the Tivoli® Dynamic Workload Broker Web Console or in the Job Brokering Definition Console - see the Tivoli® Dynamic Workload Broker User's Guide for more information).
JOBREC
   JOBCMD("dynamicjob23")
   JOBUSR(tdwbuild)