1. Tivoli Workload Scheduler for z/OS Dependencies matching criteria Mandatories dependencies

2. IBM Presentation Template Full Version
Business Scenario
Customers need a more flexible way to define dependencies.
Some scenarios cannot be addressed, using “Closest Preceding” matching criteria.
For example:
Job A runs on Friday and job B runs every day. The user wants job B to depend on job A only when job B runs on Friday.
Job A is added dynamically. If an instance of job B is going to start within the next 3 hours, the user wants job A to wait for it.
Users that work in mixed TWSz and TWSd environments would prefer a uniform behavior.

3. Matching criteria: Closest Preceding (already existing) Same Day (new)
IBM Presentation Template Full Version
Matching criteria:
Closest Preceding (already existing)
Predecessor is the closest preceding the IA of the job stream instance that includes the dependency.
Same Day (new)
Predecessor is the closest preceding (or following) the IA of the Job stream instance including the dependency within the same day.
Relative interval (new)
Predecessor is the closest to the IA of the Job stream instance including the dependency within a specified interval. The interval is expressed as an offset (hours and minutes) before or after the input arrival of the dependent instance.
Absolute interval (new)
Predecessor is the closest to the IA of the Job stream instance including the dependency within a specified interval. The interval is expressed as a time (HH:MM) at a specific number of days before or after the day of the dependent instance.

4. IBM Presentation Template Full Version
Example 1:
Job A runs on Friday and job B runs every day. The user wants job B to depend on job A only when job B runs on Friday.
AD definition for job B:
Predecessor A:
Resolution criteria: S same day

5. IBM Presentation Template Full Version
Example 2:
Job A is added dynamically. If an instance of job B is going to start within the next 3 hours, the user wants job A to wait for it
AD definition for job A::
Predecessor B:
Resolution criteria: R relative interval:
before IA <==> + 003:00 after IA

6. Mandatory Dependencies
IBM Presentation Template Full Version
Mandatory Dependencies
If no Job stream instance resolves the dependency and the dependency is mandatory, the dependent instance cannot start (current behavior does not add missing dependencies so that successor can start) .
The “IsMandatory” attribute will be defined at operation dependency level in the AD data base with following allowed values:
P: plan
At plan creation time, if the predecessor is not found, the plan fails
At ad hoc add, if the predecessor is not found the add fails
C: Control
At plan creation time, if the predecessor is not found, a “pending mandatory”
predecessor is added
At ad hoc add, if the predecessor is not found if the predecessor is not found, a
“pending mandatory” predecessor is added
N: No (default)

7. Mandatory Dependencies KEY POINTS:
IBM Presentation Template Full Version
Mandatory Dependencies KEY POINTS:
Similar to PENDING PREDECESSORS:
When a job is added to the plan (via DP batch or ad hoc add) the unresolved predecessors are added as mandatory pending predecessors if mandatory type is C (value get from AD)
It is represented in the plan like a dummy occurrence with status M without operations not visible by user (for pending predecessors the status is P)
But different:
MANDATORY PENDING predecessors represent a future job that could never be added, while PENDING ones refer to a specific occurrence existing in LTP but not yet in CP.
The mandatory pending predecessor IA is set to the right side of matching time interval

8. Mandatory Dependencies KEY POINTS:
IBM Presentation Template Full Version
Mandatory Dependencies KEY POINTS:
DIFFERENT SUCCESSOR RESOLUTION:
all matching are solved
The resolution time interval range of mandatory pending predecessor is stored in plan (XD file) to be used later to solve it
When a job with an IA matching the previously stored time interval is added to the plan the dependency is solved and the real job replaces the mandatory pending one
All matching mandatory predecessors are solved

9. New matching criteria KEY POINTS
IBM Presentation Template Full Version
New matching criteria KEY POINTS
The match before IA are always preferred if found
To avoid unwished match with jobs after IA:
User can specify the number of days to keep info about removed completed occurrence from the plan (0 to 7 days)
( BATCH Options new keyword)
This info is used to consider solved a dependency if a removed completed occurrence match is found before IA