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 HCL Workload Automation for Z.In theOPERATIONS
ISPF panel of HCL Workload Automation for Z, 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 namedSAPJOB
. This is the HCL Workload Automation for Z job that drives the running of on SAP R/3 job (namedBAPRINT46B
as shown in the next example). It shows as an extended agent job because the associated workstation is an extended agent workstation namedR3XA
.For each job, create a member in theSCRIPTLIB
of HCL Workload Automation for Z with details about the job in aJOBREC
statement. A SAPJOB member was created for the job of the previous example. It contains aJOBREC
statement like this:
The string inJOBREC JOBCMD('/-job BAPRINT46B -user MAESTRO -i 14160001 -c C') JOBUSR(twsila)
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 inJOBCMD
.The following example is for a PeopleSoft job. The entire string that follows theJOBCMD
keyword must be enclosed within quotation marks ("), because for PeopleSoft jobs single quotes are already used in the string.JOBREC JOBCMD("/ -process XRFWIN -type 'SQR Report' -runcontrol IWS") JOBUSR(PsBuild)
- HCL Workload Automation for Z agents
- For information about the jobs definition for agent with z-centric capabilities, see Scheduling End-to-end with z-centric capabilities.
The arguments of
JOBCMD
differ by application.
For details, see: