Defining jobs using the command line

You can also define jobs using the composer command line of HCL Workload Automation.

Dynamic agents

The following example describes an HCL Workload Automation job named DYN_JOB_R3_0001 defined in the folder name SAPJOBS, that runs on a dynamic agent workstation named NC112015_1. The HCL Workload Automation launches a job in an SAP environment named JOB_APPS_93.

NC112015_1#/SAPJOBS/DYN_JOB_R3_0001
 TASK
<?xml version="1.0" encoding="UTF-8"?>
<jsdl:jobDefinition 
     xmlns:jsdl="http://www.abc.com/xmlns/prod/scheduling/1.0/jsdl" 
     xmlns:jsdlxa="http://www.abc.com/xmlns/prod/scheduling/1.0/jsdlxa" 
                   name="r3">
  <jsdl:application name="r3" plugin="xajob">
    <jsdlxa:xajob accessMethod="r3batch" target="NW73LIN_r3batch">
            <jsdlxa:taskString>/ -job JOB_APPS_93 -i 14514200 -c c 
                 -flag ENABLE_APPL_RC </jsdlxa:taskString>
        </jsdlxa:xajob>
  </jsdl:application>
</jsdl:jobDefinition>
 RECOVERY STOP

Extended agents

The following example describes an HCL Workload Automation job named psjob2 that runs on a PeopleSoft extended agent workstation with unique identifier named XAPS002. HCL Workload Automation logs on to UNIX operating system as psjobs and launches a job under PeopleSoft. The PeopleSoft process is named XRFWIN. If recovery is needed, HCL Workload Automation runs job recov2 and then continues processing.

XAPS002#/mypsjobs/psjob2
  streamlogon psjobs
  scriptname
   -process XRFWIN -type 'SQR Report' -runcontrol 1 -runlocationdescr PSNT
  description "peoplesoft job #2"
  recovery continue after recov2

The arguments of scriptname differ by application. For details, see:

For more information about using the composer command line to define jobs, see User's Guide and Reference.