Defining Requirements › Satisfy Requirements › Effect of Time Zone Normalization

Effect of Time Zone Normalization

As stated in the previous topic, the successful job completion of a predecessor job under the control of CA WA CA 7 Edition is one of the requirements that the system automatically tracks and satisfies.

Without time zone normalization, or if you specify TZPREDS=EXEC on the SMF initialization statement, the start and end times used to calculate this initial requirement are the time zone where the job executed and the time zone where CA WA CA 7 Edition is running.

With time zone normalization, if you specify TZPREDS=CA7 on the SMF initialization statement, the job’s start and end times are normalized to the time zone where CA WA CA 7 Edition is running.

For example, you have job JOBAAA, and you are specifying predecessor job JOBPPP. When you specify job JOBPPP using panel DB.3.2, you can also enter lead time for that job. This lead time (also known as look back time) specifies that since the last run of job JOBAAA, JOBPPP has started and completed successfully within the last nn hours. Values for nn range from 1 to 98.

For this example, the current time in New York is 1730 and in California it is 1430. JOBAAA last ran in New York at 1615. The LEADTM specified for JOBPPP is 2. The previous run of JOBPPP ran in California and ended at 1215.

Without time zone normalization, the difference between 1615 and 1215 is four hours and the initial requirement is not satisfied. With time zone normalization, the normalized end time for JOBPPP is now 1515 (New York time), and the difference is only one hour. The initial requirement is satisfied.