adddep sched

Adds dependencies to a job stream.

You must have adddep access to the job stream. To include needs and prompt dependencies, you must have use access to the resources and global prompts.

Syntax

{adddep sched | ads} = jstreamselect
     ;dependency[;...]
     [;noask]

Arguments

jstreamselect
See Selecting job streams in commands.
dependency
The type of dependency. Specify one of the following. Wildcard characters are not permitted.

at=hhmm[timezone | tz tzname][+n days | mm/dd[/yy]] | [absolute | abs]

carryforward

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

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

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 add status or output conditions, but no joined dependencies.

limit=limit

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

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

priority[=pri | hi | go]

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

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

noask
Specifies not to prompt for confirmation before taking action on each qualifying job stream.
Note:
  1. If you add a dependency on a job stream to another job stream twice, only one dependency is considered.
  2. When using the deadline keyword, ensure the bm check deadline option is set to a value higher than 0 in the localopts configuration file on the workstation you are working on. You can define the bm check deadline option on each workstation on which you want to be aware of the deadline expiration, or, if you want to obtain up-to-date information about the whole environment, define the option on the master domain manager. Deadlines for critical jobs are evaluated automatically, independently of the bm check deadline option.

    For more information about the bm check deadline option, see Setting local options.

  3. If you add a dependency to a job stream after it has completed, it is not evaluated. However, any subsequent reruns of the job stream will process the dependency correctly.

Comments

  • If you do not specify a value for priority, the job stream reverts to its original scheduled priority.
  • If you do not specify a value for limit, the value defaults to 0.
  • If you do not specify a workstation in follows, needs, or opens, the default is the workstation on which the job stream runs.
  • You cannot use this command to add a resource or a prompt as dependencies unless they already exists in the production plan. To see which resource and prompts exist in the plan refer to showresources and showprompts.

Examples

To add a prompt dependency to job stream sked9(0900 02/19/06), stored in folder myfolder, run the following command: 
ads myfolder/sked9(0900 02/19/06) ; prompt=msg103
To add an external follows dependency to job JOBB in job stream CPUA#SCHED_02(0600 02/24/06) and a job limit to job stream CPUA#TEST(0900 02/19/06), run the following command: 
ads=CPUA#TEST(0900 02/19/06) ; follows CPUA#SCHED_02(0600 02/24/06).JOBB; limit=2

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 the job stream to which you want to add a dependency and click the Dependencies....
  7. In the Dependencies panel, expand a dependency section and click the button corresponding to the dependency action you want to add.