submit job

You can use the submit job command to launch a job.

Overview

You can use the submit job command to start a job and if needed, with pre-defined conditions. You must have submitdb access for the job to run the command. If you want to use the alias keyword for the job, make sure the job name in the database is specified along with the keyword.

You can also perform this action from any workstation other than the master domain manager. In such cases you must meet the following requirements:

Valid credentials defined in the useropts file to connect to the master domain manager through WebSphere Application Server Liberty Base.
Authorized to perform submit commands in the security file stored on the master domain manager.

If you submit a shadow job, for more information see Defining and managing cross dependencies.

Syntax and command line options

Before you run the command, you must specify options such as job name and required permissions. There are mandatory and optional parameters which you can use to schedule the start of a job. You can enter the command as follows:

ocli plan submit job|sbj = <workstation#><[folder/><jobname><alias[=name]>
<into=[[folder/]workstation#]{jobstream_id;schedid | [folder/]jobstreamname([hhmm[date]])}><joboption[;...]><vartable=tablename><noask>

You can add the parameters according to the specific results you want to achieve. The only mandatory parameter is jobname. The details required with each parameters are as follows:

workstation

Specify the workstation to run the job on. You can use wildcard characters. If you use wild cards, the job starts on all matching workstations. If you do not specify a workstation, the job runs on the default workstation.

jobname

You must specify the name of the job to start. You can use wildcard characters. I you use wildcard characters all matching jobs are submitted. If the job is already in plan, and submitted into the same job stream, you must use the alias keyword to assign a unique name.

alias=name

You can specify a unique name for the job which can be used in place of jobname parameter. If you add the alias keyword without specifying a name, a name is created using the first 5 alphanumeric characters followed by a random ten digit number.

into=[folder/]jobstream_instance

Specify the jobstream instance to launch the job. You can also provide the folder that contains the job stream definition. If you do not specify any jobstream, the jobs are added to the default job stream JOBS. The associated files of JOBS job stream are always located at the root (/).

Select the job stream instance as follows:

[[folder/]workstation#][folder/]jobstreamname([hhmm[ date]])

[[folder/]workstation#]jobstream_id ;schedid

joboption

The optional parameters to customize the launch of a job. You can specify one or more of the following options.

Table 1. joboption
Options	Reference
`at= hhmm [timezone\|tz tzname] [+n days \| [mm/dd \| mm/dd[/yy]]]`	at
`deadline= time [timezone \| tz][+n day[s] [mm/dd \| mm/dd[/yy]]]`	deadline
`follows=[workstation#]{jobstreamname[time [mm/dd \| mm/dd[/yy]]][.job \| @] \| jobstream_id.job;schedid}\| job[,...] [if 'condition_name[\| condition_name][\| ...]']`	The scheduler classifies follows dependencies as internal when they are specified only with the job name and are classified as external when they are specified in `workstation#[folder/] jobstreamName.jobName` format. For more information, see follows.
`maxdur=[time] [onmaxdur action]`	maxdur
`mindur=[time] [onmindur action]`	mindur
`until time [timezone\|tz tzname][+n day[s]] \| [;onuntil action]`	until
`confirmed`	confirmed
`critical`	critical
`nocheck`	If you use the parameter in command line option, no check will be performed when an object mentioned in the dependency is not found. The job will continue to run without the dependency. Restriction: Not supported for internet work dependencies.
`recovery`	You can specify the recovery options for the job. For more information, see recovery
`recoveryjob`	You can enter the name of the job, if it is different from the job which you have specified in jobname. To add this parameter you must have the submit access for the job specified.
`abendprompt "text"`	You can write a text which you want to display, when a job ends abnormally. The text an contain up to 64 characters. For more information, see abendprompt "text".
`vartable=tablename`	You must specify the name of the variable table, if you are not using the default variable table to run the job. For more information, see Customizing your workload using variable tables. Note: You can use the `vartable=tablename` to substitute the following keywords. `opens` `prompt` `abendprompt` Enclose the variable between carets (^), and then enclose the entire string between double quotation marks. If the variable contains a portion of a path, ensure that the caret characters are not immediately preceded by a backslash (\) because, in that case, the `\^` sequence could be wrongly interpreted as an escape sequence and resolved by the parser as caret character. If necessary, move the backslash into the definition of the variable between carets. Restriction: If the variables in the job definition are specified in ${variablename} format, the variable table is not resolved. For more information, see ${variablename}.

noask

When you add the option as an argument the agent will not ask for confirmation before taking action on each qualifying job.

Examples

To submit the test job into the job stream JOBS, run the following command:
```
ocli plan sbj = test
```
To submit a job with an alias of rptx4 and place the job in the job stream reports with at time of 5:30 p.m., run the following command:
```
ocli plan sbj = rjob4;alias=rptx4;into=reports;at=1730
```
To submit the test job in the job stream ORDERS that is found in the folder named ONLINE, run the following command:
```
ocli plan sbj = test;into=/ONLINE/orders
```
To submit job txjob3 on all workstations whose names begin with site, run the following command:
```
ocli plan sbj = site@#txjob3;alias;noask
```