deldep sched
You can use the deldep schedcommand to delete the dependencies from a job stream.
Overview
To remove the dependencies from a job stream, you must have the deldep access to the job stream. For more information about security access roles, see Security role definition.
Syntax and command line options
ocli plan deldep sched | dds = <jstreamselect><dependency><noask>
You can add the dependency according to the specific results you want to accomplish. The details that are required with each parameters are as follows:
jstreamselectSpecify the job stream to update, by means of attributes and qualifiers. For more information, see to Selecting job streams in commands.
dependencyworkstation
, jstreamname
,
jobname
, resource
, filename
,
and promptname
. When you rerun the job stream,
the deleted dependencies are not considered. - When you delete the dependency
priority
, the job reverts to its original scheduled priority. - When you delete an
opens
dependency, you can only include the base file name and the Orchestration CLI performs a case-insensitive search for matching files, ignoring the directory names. The dependencies on all the matching files are deleted.
follows
dependency. The command
will be rejected.Command | Reference |
---|---|
at= time[timezone | tz][+n day[s] | [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[/yy]]][.job | @] | jobstream_id.job;schedid}| job[,...]
[if 'condition_name[| condition_name][| ...]'] |
follows |
until time [timezone|tz tzname][+n day[s]] |
[;onuntil action] |
until |
When you add the option as an argument the agent will not ask for confirmation before taking action on each qualifying job.
Examples
- To delete all follows dependencies from job stream
sked3(1000 04/19/06)
, run the following command:ocli plan dds sked3(1000 04/19/06);follows