submit docommand
You can use the submit docommand command to schedule the start of a command as a job.
Overview
You can use the command to schedule the start of a command as a job and if needed, with pre-defined conditions. You must have submit 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.
- 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
submit docommand | sbd = <[folder/]workstation#]><"cmd"><alias[=name]>
<[into=[[folder/]workstation#]{jobstream_id;schedid |[folder/]jobstreamname([hhmm[date]])}]><[joboption[;...]>
'\='\
. hello
you must issue the
following
command:%sbd "set var1\"=\"hello"
You can add the parameters according to the specific results you want to achieve. The only mandatory parameter is cmd. The details required with each parameters are as follows:
workstationSpecify the name of the workstation on which you want to run the job. You can use wildcard characters and in such cases, the job is started on all the matching workstations. You cannot specify a domain or workstation class.
cmdYou must specify a valid command and can use up to 255 characters. The command is treated as a job and all the job rules are applicable. You must enclose the entire command in double quotation marks (").
into=[folder/]jobstream_instanceSpecify the jobstream instance to start a 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]])
or [[folder/]workstation#]jobstream_id ;schedid
The optional parameters to customize the launch of a job. You can specify one or more of the following options.
Options | Reference |
---|---|
at= hhmm [timezone|tz tzname] [+n days | [mm/dd |
mm/dd[/yy]]] | [absolute | abs] |
at |
deadline= time [timezone | tz][+n day[s] [mm/dd |
mm/dd[/yy]]] |
deadline |
follows=[workstation#]{jobstreamname[time
[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. follows |
maxdur=[time] [onmaxdur action] |
maxdur |
mindur=[time] [onmindur action] |
mindur |
logon |
You can specify the user name to run the job. |
until time [timezone|tz tzname][+n day[s]] |
[;onuntil action] |
until |
confirmed |
confirmed |
critical |
critical |
Examples
- To submit a rm command into the job stream
JOBS
with afollows
dependency, run the following command:submit docommand = "rm apfile";follows sked3
- To submit a sort command with the alias
sortit
and place the job in the job streamreports
with an at time of5:30 p.m.
, run the following command:sbd "sort < file1 > file2";alias=sortit;into=reports;at=1730
- To submit chmod commands on all workstations with names
beginning with
site
, run the following command:sbd site@#"chmod 444 file2";alias