If a jobset has a dynamic predecessor requirement (the default) that specifies a job, jobset, or trigger that is not in the tracking file (not currently scheduled to run) at the time the predecessor requirement is evaluated, that predecessor requirement is automatically satisfied through an implicit posting. In effect, it is ignored. If the predecessor requirement type is static, no implicit posting takes place. The jobset remains in "wait on predecessor" state (WPRED) until the predecessor requirement is satisfied.
The reason the CA NSM JM Option performs this implicit posting with dynamic predecessor requirements is simple. To have a dependency on a job that does not exist is illogical, because any job with such a predecessor dependency would never run. As such, if the CA NSM JM Option detects such a condition—a predecessor requirement referencing a job not scheduled to run (that is, does not exist in the current workload)—it ignores the illogical predecessor requirement and continues to evaluate eligibility.
You can use static predecessor requirements in those instances where a jobset must not run unless its predecessor job completes first. A jobset can have both static and dynamic predecessor requirements, but cannot reference the same predecessor requirements as both dynamic and static.
|
Copyright © 2010 CA.
All rights reserved.
|
|