release sched

Releases job streams from dependencies.

You must have release access to the job stream.


{release sched | rs} jstreamselect


See Selecting job streams in commands.
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]


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#]

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.


needs[=[num] [[folder/]workstation#][folder/]resource[,...]]



prompt[="[: | !]text" | [folder/]promptname[,...]]

until[=time [timezone|tz tzname][+n day[s]] [;onuntil action]]

Specifies not to prompt for confirmation before taking action on each qualifying job stream.


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.


To release job stream instance with jobstream_id 0AAAAAAAAAAAABSE, stored in folder myfolder, from all of its dependencies, run the following command:
rs myfolder/0AAAAAAAAAAAABSE; schedid
To release job stream sked5(1105 03/07/06) from all of its opens dependencies, run the following command:
rs sked5(1105 03/07/06);opens
To release all job streams on workstation site3 from their dependencies on job stream sked23 contained in the TEST folder, on workstation main, run the following command:
where TEST is the folder where the job stream is located.

See also

From the Dynamic Workload Console you can perform the same task as follows:
  1. In the navigation bar at the top, click Monitoring and Reporting > Workload Monitoring > Monitor Workload.
  2. Select an engine.
  3. In Object Type, select Job Stream.
  4. From the Query drop-down list, select All Job Streams in plan or another task to monitor job streams.
  5. Click Run to run the monitoring task.
  6. From the table containing the list of job streams, select one or more job streams and click Release Dependencies.