Coding Each AOF Rule Type › Time-of-Day Rules › )TOD—Event Definition Section of TOD Rules › Rules Governing the Coding of TOD Event Specifiers

Rules Governing the Coding of TOD Event Specifiers

The following rules govern the coding of TOD event specifiers:

• The number of event specifiers that may be coded is 1 to 10.
• The number of event specifiers allowed per line is 1.
• Uppercase or lowercase letters are acceptable.
• Blank lines are permitted between time event specifiers.
• Any number of blanks is permitted between qualifiers.
• An event specifier may begin in any column, except on the )TOD line.
• An event specifier may use the entire line (72 characters).
• Because TOD rules allow multiple spec lines, a section header must follow them before comments can be used. Either a )INIT card must be inserted prior to the comment card or the comment must be moved after the )PROC card.
• If your Start-time and Stop-time are exact dates, for example 03 JUN 2002 and 04 JUNE 2002, the End-time must be in the future. The rule does not enable if End-time has already expireTime defaults:

  If the starting date/time specification contains a time, and the ending date/time specification does not, the time part of the starting date/time specification is used for the ending date/time specification. For example, given the following starting and ending specifications, the rule would execute Monday, Tuesday, Wednesday, Thursday, and Friday at 08:00 on each day:

  )TOD MONDAY 8:00, DAY, FRIDAY
  

  If the Start-time contains only a time value, with an interval unit of HOURS, MINS, or SECS, and no End-time is specified, then the default End-time would be midnight each day. For example, given the following TOD specifications, the rule would execute starting at 15:00 every day, and then execute every 5 minutes until midnight:

  )TOD 15:00,5 MINS
  

  If the Start-time contains a day of the week value, with an interval unit of HOURS, MINS, or SECS, and no End-time is specified, then the default End-time would be Sunday at 00:00:00. For example, given the following TOD specifications, the rule would execute starting on Tuesday 08:00, and then execute every 1 hour until Sunday at 00:00:00 and resume again on Tuesday at 08:00:

  )TOD TUESDAY 08:00,1 HOUR
  

  If the TOD specifier contains just a starting specification that contains a day of the week and time value, then the default End-time would be on a week boundary. For example, given the following TOD specifier, the rule would execute every Friday at 06:00:00:

  )TOD FRIDAY 06:00:00
  

• Completeness and order of date and time: date/time specifications may omit the date or the time, and they may be coded in any order; use a blank to separate the date and the time, as shown in the following example:

  21 JAN 2002 1:20
  

  Omitting the executing date causes the rule to execute every day. If the time is omitted, CA OPS/MVS assumes it to be 00:00:00, midnight (there is an exception, which is noted in the next rule).

• Start/end order: the starting date/time specification must indicate a point in time that is before the ending date/time specification. The following is an example that will not enable because the AOF week starts on Sunday and ends on Saturday:

  )TOD FRIDAY,DAY,MONDAY
  

  The correct method to create a TOD rule that executes at midnight on Friday, Saturday, Sunday, and Monday is:

  )TOD    FRIDAY,DAY,SATURDAY
          SUNDAY,DAY,MONDAY
  

• Format compatibility (date/time): the ending date/time specification must be the same type as the starting date/time specification; for example, you cannot code:

  )TOD MONDAY,,2002/10/14
  

  because the ending date/time specification is in day-of-year format while the starting date/time specification is in day-of-week format.

• Although you can specify the msgallow, catchval, and synch options only once in a rule, you may specify them on any line of the TOD-event definition section. You do not have to specify these three qualifiers on the same line with each other; you may specify them in any combination you wish. The values of these qualifiers apply to all event specifier values in that rule.

  Note: CA recommends that you code these options on the first event specifier.