deldep sched

Deletes dependencies from a job stream.

You must have deldep access to the job stream.

Syntax

{deldep sched | dds} jstreamselect
     ;dependency[;...]
     [;noask]

Arguments

jstreamselect
See Selecting job streams in commands.
dependency
The type of dependency. Specify at least one of the following. You can use wildcard characters in workstation, jstreamname, jobname, resource, filename, and promptname, with the exception of workstation when used in a follows dependency.

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][| ...]']
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.

limit

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

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.

Examples

To delete a resource dependency from job stream sked5(0900 02/19/22), run the following command: 
dds sked5(0900 02/19/22);needs=2 tapes
To delete all follows dependencies from job stream sked3(1000 04/19/06), run the following command: 
dds sked3(1000 04/19/22);follows

See also

  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 the job streams 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.