OA45353: CHRON TIMER DOES NOT WORK AS EXPECTED. TIMER SET FOR EVERY DAY OF WEEK BUT SUNDAY (NOT SUN) DOESN'T RUN SUNDAY (OK) NOR MONDAY.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• CHRON timer does not work as expected. Timer set for every day
  of week but Sunday (NOT SUN) doesn't run Sunday (OK) nor Monday.
  

Local fix

• Circumvention would be to set the AT for the timer to
  00:00:01, which would cause the timer to pop at 1 second
  after midnight (if it's not crucial that the time be
  exactly midnight), and would also make the defer of the
  timer work out correctly.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of Tivoli NetView for z/OS who use *
  *                 the CHRON command.                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a timer that is defined using the  *
  *                      CHRON command is set to not pop on      *
  *                      certain days of the week (such as when  *
  *                      NOT is used for the DAYSWEEK keyword),  *
  *                      and the timer would pop exactly at      *
  *                      midnight on one of those days, the      *
  *                      timer is set to next pop one additional *
  *                      interval beyond the next midnight. For  *
  *                      example, if the timer's interval is     *
  *                      every 15 minutes, the next scheduled    *
  *                      pop time would be 00:15:00 instead of   *
  *                      midnight itself.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Routine DefCalNewPop in module DSITIMGT is responsible for
  setting up the new pop time for a CHRON timer when other code
  has determined that the timer is not to pop on that day. It
  performs calculations based on the current time, the local
  midnight time, and the timer interval. However, when the results
  of the calculations determine that the next pop time is the
  following day's midnight exactly, the code mistakenly adds an
  additional interval amount to the pop time. So, if the interval
  is 15 minutes, the pop time would be 00:15:00 instead of
  midnight, and likewise if the interval is one day, the pop time
  would be midnight on the following day.
  

Problem conclusion

• Routine DefCalNewPop in module DSITIMGT is being changed to
  correctly set the pop time for the next day's midnight when it
  should be.
  

Temporary fix

Comments

APAR Information

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

  OA44950

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

  UA74273

Modules/Macros

• DSITIMGT
  

Fix information

• Fixed component name

  AUTO CNTL NETV

• Fixed component ID

  5698LSA01

Applicable component levels

• R11B PSY UA74273

     UP14/10/21 P F410

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.