release job

You must have release access to the job.

Syntax

{release job | rj} jobselect
     [;dependency[;...]]
     [;noask]

Arguments

jobselect

Specifies the job or jobs to be released. See Selecting jobs in commands.

dependency

The type of dependency. You can specify one of the following. You can use wildcard characters in workstation, jstreamname, jobname, resource, filename, and promptname.

at[=time | lowtime | hightime | lowtime,hightime]

confirmed

deadline[=time[timezone | tz tzname][+n days | mm/dd[/yy]]]

every

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.

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.

Comments

The command applies only to jobs that are in the HOLD state; that is, jobs that are waiting for the resolution of a dependency. Note also that the dependency is released only for the current run of the job and not for future reruns (the permanent release from a dependency can be obtained with the deldep command).

When you release 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 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 from a priority dependency, the job reverts to its original scheduled priority.

Released dependencies remain in effect when running the rerun command.

See also