deldep job

Deletes dependencies from a job.

You must have deldep access to the job.

Syntax

{deldep job | ddj} jobselect
     ;dependency[;...]
     [;noask]

Arguments

jobselect
See Selecting jobs in commands.
dependency
The type of dependency. Specify at least one of the following. You can use wildcard characters in workstation, jstream, job, 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][| ...]']
Note: Internetwork dependencies do not support folders, therefore, the network agent workstation, and the jobs and job streams running on them, cannot be defined in a folder different from the root (/). Folders are supported on all other workstation types as follows: 
 [follows {[[folder/]workstation#][folder/]jobstreamname[.jobname]

follows=[[folder/]workstation#][folder/]{jobstreamname[hhmm [mm/dd[/yy]]][.job | @] | jobstream_id.job;schedid}| job[,...] [if 'condition_name[| condition_name][| ...]']

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 delete 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.

maxdur=[hhhmm] [onmaxdur action]

mindur=[hhhmm] [onmindur action]

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

opens[=[[folder/]workstation#]"filename"[(qualifier)][,...]]

priority

prompt[="[: | !]text" | 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

If you delete priority, the job reverts to its original scheduled priority. When you delete 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 deleted.

Deleted dependencies no longer remain in effect when running the rerun command.

To delete all the follows dependencies from the jobs contained in a specific job stream, specify the follows keyword as: 
follows=job_stream_name
Do not use a wildcard in this case (such as follows=job_stream_name.@ because the command will be rejected.

Examples

To delete a resource dependency from job job3 in job stream sked9(0900 02/19/06), run the following command: 
ddj sked9(0900 02/19/06).job3 ; needs=2 tapes
To delete all external follows dependency from job stream CPUA#TEST(0900 02/19/06), run the following command: 
ddj=CPUA#TEST(0900 02/19/06).JOBA ; follows

See also

From the Dynamic Workload Console you can perform the same task as follows:
  1. From the Monitoring and Reporting menu, click Monitor Workload.
  2. Select an engine.
  3. In Object Type, select Job.
  4. From the Query drop-down list, select All Jobs in plan or another task to monitor jobs.
  5. Click Run to run the monitoring task.
  6. From the table containing the list of jobs, select the job from which you want to remove a dependency and click Dependencies....
  7. In the Dependencies panel, select the dependency you want to delete and click Delete.