Syntax diagram for xajob job type

Purpose

If you set JOBTYPE to /xajob/access method name, you can run a job on an extended agent:

This section provides detailed information about the syntax diagram for the xajob job type.

Format

Parameters

ENVVARid(environment variable name=value)

The environment variable that the task launcher must set before submitting the job. You can specify a series of ENVVARid keywords, where id is a unique numeric value, including null and zero.

Use the following format, which is case sensitive:

ENVVARid(environment variable name=value)

Where:

environment variable name: The name of the environment variable.
value: The value associated with the environment variable.

JOBPWD(YES|NO|AGENT)

Specifies if the user name entered in JOBUSR or set by using the job-submit exit EQQUX001 is associated with a password.

If you set JOBPWD to YES, HCL Workload Automation for Z searches for the user password in the USRPSW keyword of the USRREC statement (for details, see Customization and Tuning).

If you set JOBPWD to AGENT, this means that the password is resolved locally on the agent. The password must have been defined on the agent by means of the param command. This feature is available independently of the operating system of the workstation.

Typically, the password is required for users who schedule jobs to run on Windows™ workstations. Set JOBPWD to NO if the user works with UNIX™ workstations and if no password is required.

JOBTYPE(/xajob/access method name|/j2ee/jms|/web service|/file transfer|/database|/java)

To run an xajob, specify /xajob/access method name. For information about the other types of job, see the specific section for each job type. This keyword is required.

/xajob/access method name: The name of the access method hosted by the extended agent on which you want to submit the job. For example, for a job to be submitted on a SAP extended agent, this value might be /xajob/r3batch. If you set this keyword, the JOBCMD keyword value is ignored.

JOBUSR(user name)

The name of the user submitting the job.

If the user schedules jobs to run on Windows™ workstations, ensure that a user password is also defined (see the JOBPWD keyword).

If you are defining a Windows™ domain user, use the following format:
```
JOBUSR(domainName\user1)
```
If you are defining a Windows™ user in the username@internet_domain format, use the following format:
```
JOBUSR('administrator@mywindom.com')
```

To specify the user name, you can also use the job-submit exit EQQUX001. This user name overrides the value specified for JOBUSR. In turn, the value specified for JOBUSR overrides the value specified for USRNAM in the USRREC statement.

WSNAME(workstation_name)

The name of the workstation from which user name and password must be retrieved. User name and password can be specified in the statement, using the JOBUSR and JOBPWD keywords, or can be associated to a workstation with the USRREC statement. With the WSNAME keyword, you can specify a workstation where the user name and password are stored, which is different from the workstation where the job runs.

Examples

The following is an example of a JOBREC statement to un a job using the r3batch access method. The content of the JOBTYPE keyword is case sensitive:

//JOBREC        
JOBTYPE(/xajob/r3batch)
ENVVAR10(VAL=10)
//END JOBREC    
-JOB SAPJOB -USER SAPUSER