Fellow [DEC]event watchers,
For many of you this may be an old news, but some may not have noticed yet
that DECevent does not recognize leap year. I examine my binary errorlog
file every few hours, search for some key words and take action accordingly.
Last night when the errorlog was analyzed by DECevent it did not recognize
dia -t s:29-FEB-2000 and read the errorlog file form the begining and start
taking defined action on
each key word it found, paging, e-mails, even filling disks "What a
LeapYear". Per all documentations DECevent is supposed to be Y2K compliance.
I also tried the latest and greatest version 3.1 currently available on the
DECevent website, which also has the same problem as the version 3.0 or
earlier.
Problem:
#dia -a -t s:29-feb-2000
Workaround:
#dia -a -t s:28-feb-2000
I hope this will fixed by Year 2004 --Per DECevent, I am OnCall that day.
Thanks,
Ronny Eliahu
The Walt Disney Co.
Disney WorldWide Services
Disney Studios, Burbank CA
Received on Tue Feb 29 2000 - 21:58:17 NZDT