|
|
|
|
|
Conditions are generally used to create job dependencies. In the previous chapter you saw that when IDJOB1 ended OK, it set an OUT condition (IDJOB1-ENDED-OK) that satisfied the prerequisite IN condition to IDJOB2. This is necessary because IDJOB2 could not be submitted until IDJOB1 ended OK.
Earlier in this chapter you defined a DO COND condition. Both OUT and DO COND are post-processing statements that add or delete conditions. But the OUT condition is only added or deleted when the job ends OK; the DO COND condition is only added or deleted when the criteria in the ON block are satisfied.
As mentioned in the last chapter, every condition has an associated date. This can be an explicitly defined date, such as 0909, but more commonly, it is a keyword that represents an actual date. For example, the date keyword ODAT stands for the original scheduling date of the job. The meaning of original scheduling date is discussed in AutoEdit and JCL, and is referred to in the discussion of date concepts in the Control-M for z/OS User Guide.
A condition is actually identified by the combination of its name and date. Two conditions having the same name but different dates are considered two different conditions. In the last chapter, you wanted the run of IDJOB2 to be dependent on the run of IDJOB1 from the same day. Therefore, not only did the condition names of both jobs have to match, but so did the dates. Use of the keyword ODAT for both the IN and the OUT condition ensured that they match. Had they run on different original scheduling dates, there would have been no match.
In this chapter you create another type of dependency—a dependency between different runs of the same job on different dates. IDJOB3 cannot run this month unless it successfully ran last month. The same condition name is used (IDJOB3-ENDED-OK), but with different dates for the IN condition and OUT condition.
Parent Topic |