OA50351: MODIFY THE CHRON COMMAND TO NOTIFY AN OPERATOR IF A TIMER IS SKIPPED DUE TO TIME CHANGE.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The customer has a timer that is scheduled to run at 03:00:01
  and when daylight savings time change occurred it was after
  that exact second, the timer time was in fact earlier than the
  current time. Since the timer is an EVERY this causes the timer
  to be set for the next interval and the current time.  There
  should be some type of notification issued if this happens.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the CHRON command in Tivoli     *
  *                 NetView for z/OS.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the local time is set forward      *
  *                      (such as for Daylight Savings Time in   *
  *                      the spring), EVERY timers may be        *
  *                      skipped, but there is no notification   *
  *                      when this occurs.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the local time changes (for example, with the SET CLOCK or
  SET TIMEZONE command), the next time the DSIMONIT task wakes up
  (which is every 5 seconds), the difference is noticed, and the
  DSITIMMT task is notified. The DSITIMMT task then adjusts all
  timers defined with the LOCAL attribute. If the new time is
  later than the old time, EVERY timers may be skipped, if they
  are scheduled to run in the time that doesn't exist or in the
  few seconds that the NetView program takes to notice the change.
  However, there is no notification for these skipped timers, as
  there are for other events when using CHRON.
  

Problem conclusion

• Module DSITIMGE is being changed to recognize when an EVERY
  timer is skipped because of a local time change, and to send
  notification message BNH549I with a new eventname of SKIP.
  Module DSITIMGM is being changed to send BNH549I with an
  eventname of SKIP to all operator IDs that are notified for the
  IGNORE event.
  The description of the IGNORE event under the NOTIFY keyword of
  the CHRON command in the IBM Tivoli NetView for z/OS V6R2M1
  Command Reference Volume 1 (A-N) manual (SC27-2847-07) should be
  changed as follows:
    - The first sentence should be changed to read as follows:
        A command failed to be scheduled because the required task
        was not active or the local time changed to cause the
        timer to be skipped.
    - A new sentence should be added at the end of the paragraph
      which reads as follows:
        If message BNH549I is issued because the timer is skipped
        due to a local time change, the event in the message
        indicates SKIP instead of IGNORE.
  The description of message BNH549I in the IBM Tivoli NetView for
  z/OS V6R2M1 Messages and Codes Volume 1 (AAU-DSI) manual
  (GC27-2856-07) should be changed as follows:
    - A new eventname, SKIP, should be added to the Message
      Variables section which reads as follows:
        SKIP    Signifies that one or more occurrences of the
                command for timerid were not run because the local
                time changed which caused the timer to be skipped.
                The timer is scheduled to run at the next interval
                specified by the EVERY keyword.
  The following Note should be added to the Overview of Timer
  Commands subsection in Chapter 11, Timer Commands, in topic
  NetView Program Automation Facilities in the IBM Tivoli NetView
  for z/OS V6R2M1 Automation Guide (SC27-2846-04):
    Note: Updating the current local time (for Daylight Savings
    Time, for example) can affect when timers defined with the
    LOCAL attribute run. When the clock is set forward, timed
    commands might be skipped because the time they're scheduled
    to run does not exist. Conversely, when the clock is set
    backward, timed commands might run additional times because
    the time they're schedule to run repeats. Also, because it
    takes a few seconds for the NetView program to recognize when
    the local time has changed, it is safest not to schedule
    commands to run within 10 seconds of the time that the clock
    is changed to be.
  The online help for the CHRON command and for message BNH549I
  are being changed to reflect the above.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UA82523 UA82524 UA82525

Modules/Macros

•    BNH54    DSITIMGE DSITIMGM EUYCHEFP
  

Fix information

• Fixed component name

  AUTO CNTL NETV

• Fixed component ID

  5698LSA01

Applicable component levels

• R12B PSY UA82523

     UP16/08/16 P F608

• R12E PSY UA82524

     UP16/08/16 P F608

• R12J PSY UA82525

     UP16/08/16 P F608

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.