Specifies a list of dependency jobs that the manager will override for the job’s next run. After the job completes or the dependencies are modified, the manager replaces the original dependencies.
Note: Each SET JOB/NO_DEPENDENCY command that is issued for the same job overrides the previous command. For example, suppose job C is dependent on job A and job B. The following command would modify job C to remove its dependency on job A for the next job run only:
SCHEDULE> SET JOB C/NO_DEPENDENCY=(A)
When job C is run again, the following command is issued:
SCHEDULE> SET JOB C/NO_DEPENDENCY=(B)
The first command removes job C’s dependency on job A. The second command removes job C’s dependency on job B, but reinstates job C’s dependency on job A by overriding the first command. To remove job C’s dependency on both job A and job B for the next job run, you must put both job names in a list, for example:
SCHEDULE> SET JOB C/NO_DEPENDENCY=(A,B)
If you specify a dependency that is not in the job’s dependency list, the manager ignores it.
If the specified job is in DEP WAIT state and you override all of its dependencies, the job runs immediately.
Use the SCHEDULE SHOW JOBS/FULL command to display dependency jobs that the manager has overridden. The dependency jobs are displayed with brackets ([ ]) around them, as if they had completed running.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |