release sched
You must have release access to the job stream.
Syntax
{release sched | rs} jstreamselect
[;dependency[;...]]
[;noask]
Arguments
- jstreamselect
- See Selecting job streams in commands.
- dependency
- The type of dependency. Specify one of the following. You can use wildcard characters in
workstation, jstream, job, resource, filename, and promptname.
at[=time | lowtime | hightime | lowtime,hightime]
carryforward
deadline[=time[timezone | tz tzname][+n days | mm/dd[/yy]]]
follows=[netagent::][workstation#]{jobstreamname[hhmm [mm/dd[/yy]]][.job | @] | jobstream_id.job;schedid}| job[,...] [if 'condition_name[| condition_name][| ...]'][from join join_name]
Network agent workstations do not support folders, therefore neither the network agent nor the jobs or job streams running on them can be defined in folders. Folders are supported on all other workstation types, as follows:[follows {[folder/][workstation#] [folder/]jobstreamname[.jobname]
The condition_name variable indicates the name of the condition defined in the job definition. Conditions must be separated by | and enclosed between single quotes. Conditions can be status conditions, based on job status, or other output conditions, based on a mapping expression such as a return code, output variables, or output found in a job log. In each follows statement, you can specify only one dependency type: either status or output conditions. At submission time, you can release status or output conditions. If the conditional dependency belongs to a join, if the number of conditions that must be met is different from ALL, the number is automatically reduced by one.
limit
needs[=[num] [[folder/]workstation#][folder/]resource[,...]]
opens[=[[folder/]workstation#]"filename"[(qualifier)][,...]]
priority
prompt[="[: | !]text" | [folder/]promptname[,...]]
until[=time [timezone|tz tzname][+n day[s]] [;onuntil action]]
- noask
- Specifies not to prompt for confirmation before taking action on each qualifying job stream.
Comments
When deleting an opens
dependency,
you can include only the base file name, and conman performs
a case-insensitive search for matching files, ignoring the directory
names. Dependencies on all matching files are released.
For needs
dependencies,
the released job stream is given the required number of units of the
resource, even though they might not be available. This can cause
the available units in a showresources to display a negative
number.
When you release a job stream from a priority
dependency,
the job stream reverts to its original priority.
In certain circumstances, when you have submitted a deldep command, the command might have succeeded even though it is again forwarded to batchman. For more information, see Conman commands processing.
Examples
0AAAAAAAAAAAABSE
, stored in folder myfolder, from all of its
dependencies, run the following command:
rs myfolder/0AAAAAAAAAAAABSE; schedid
sked5(1105 03/07/06)
from all
of its opens
dependencies, run the following command:
rs sked5(1105 03/07/06);opens
site3
from their dependencies on job
stream sked23
contained in the TEST
folder, on workstation
main
, run the following command:
rs=site3#@;follows=main#/TEST/sked23
where TEST is the folder where the job
stream is located.See also
- In the navigation bar at the top, click .
- Select an engine.
- In Object Type, select Job Stream.
- From the Query drop-down list, select All Job Streams in plan or another task to monitor job streams.
- Click Run to run the monitoring task.
- From the table containing the list of job streams, select one or more job streams and click Release Dependencies.