Special Year-End Handling of Periodic Calendars

Jobs or missions may be improperly scheduled if both the following are true:

• a periodic calendar contains one or more periods that start in one year and continue into the next year
• the first occurrence of the matching identifier in one logical year falls within the default gap that began at the last occurrence of the matching identifier in a prior logical year, possibly as a result of changes made using optional Wish WM2888.

In such cases, the period in the prior logical year overlaps the period in the later logical year, causing a scheduled job not to run in the later logical year as expected. To avoid this problem, remove logical years from periodic calendars as soon as they are no longer needed.

Example:

• Logical year FISCAL01 extends from April 1, 2001 through March 31, 2002.
• Logical year FISCAL01 contains a period identified as Period A that has been defined to begin on December 28, 2001 and to continue through January 15, 2002.
• Logical year FISCAL02 extends from April 1, 2002 through March 31, 2003.
• Logical year FISCAL02 also contains a period identified as Period A, defined to begin on April 20, 2002 and continue through May 3, 2002.
• Job X is scheduled for the seventh day of Period A in each logical year, through the job definition DAYS=D7PA.

In a case where the default gap is 33 days, Job X runs in January 2002, and again in April 2002, as expected.

In a case where the default gap is changed from 33 days to a longer period, such as 120 days, the first day of Period A in logical year FISCAL02 occurs less than 120 days after the last appearance of Period A in logical year FISCAL01. As a result, what appears to be the seventh day in Period A in April 2002 is not recognized as such, because the "old" Period A overlaps the "new" Period A. Consequently, Job X does not run again when the user may have expected it to run.