submit sched

You can use the submit sched command to start a job stream.

Overview

You can use the command option to start a job stream and if needed, with pre-defined conditions. You must have submit access for the job stream 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.

Syntax and command line options

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

ocli plan submit sched = | sbs = <[[folder/]workstation#][folder/]jstreamname>
<[alias[=name]]><[jstreamoption[;...]]><[vartable=tablename]><[noask]>

You can add the parameters according to the specific results you want to achieve. The only mandatory parameter is jstreamname. The details required with each parameters are described below.

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.

[folder/]

You can specify the name of the job stream folder in which the job stream is defined.

jstreamname

You must specify the name of the job stream which you want to launch. You can use wildcard characters and in such cases all the matching job streams are submitted. If the job stream is already in the production plan, you must use the alias parameter to assign a unique name.

alias=name

You can specify a unique name for the job stream which can be used in place of jstreamname. If yo 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.

jstreamoption

You can customize the start of a job stream with optional parameters. You can specify one or more of the options in the following table.

Table 1. jstream options
Options	Reference
`at= hhmm [timezone\|tz tzname] [+n days \| [mm/dd \| mm/dd[/yy]]`	at
`schedtime=[hhmm [date [mm/dd \| mm/dd/yy] \| [+n days]`	schedtime
`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, seefollows.
`until time [timezone\|tz tzname][+n day[s]] \| [;onuntil action]`	until
`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 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.
`limit=joblimit`	limit

Examples

To submit the adhoc job stream included in the payroll folder on workstation site1 stored in folder myfolder, run the following command:
```
ocli plan submit sched = myfolder/site1#PAYROLL/adhoc
```
To submit job stream fox4 with an until time of midnight, run the following command:
```
ocli plan sbs = fox4;until=0000
```
To submit job stream sched3 on all workstations with names that start with site, run the following command:
```
ocli plan sbs = site@#sched3
```