We have one distributed remote data entry application that depended on
Java on NexTel hand helds that had problems because NexTel's level of
Java didn't handle the transition properly. The devices had a
less-efficient backup mode of operation that didn't depend on Java that
is being used successfully to keep the application fully functional
until either NexTel distributes the required patches or the old DST
transition date is reached (at which point all symptoms will disappear
until the next transition).
That's the worse we saw. We didn't expect anything major from DST and
our expectations were confirmed.
Doc Farmer wrote:
I was hearing the gloom 'n' doom predictions on Friday about this DST being
a "mini-Y2K" (no kidding, they actually said that on the news). However,
my PC didn't explode, the Mainframes aren't melted puddles of iron and
silicon, and the only thing I did have a problem with was figuring out how
to get the hotel's wake-up call to function properly (but with this hotel,
that's a struggle anyway, DST or no).
Any "horror stories" out there? Did anyone suffer a lack of synchronicity
(and losing your Sting collection doesn't count)? Were there dire
consequences beyond losing an hour's worth of sleep?
Answers on a post card, please...
...
--
Joel C. Ewing, Fort Smith, AR [EMAIL PROTECTED]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
