For any of you who don't know, DST changes in the USA take effect in
March. A lot of information about this is on my blog, including links
to IBM, HP, Sun, Linux, Microsoft, and other resources for details and
software patches.

While this was initated in the USA it does have global ramifications
for systems that integrate with systems in the USA. Everyone is
encouraged to research how it applies to their site and those of
end-users for whom we are all responsible. Vendors, please take this
opportunity to contact your client base to ensure they are aware of
the changes and that they have done their own investigations to ensure
their businesses are not interrupted. End-users should similarly
contact their vendors if they need assistance. This is important for
any company that has not updated their operating systems over just the
last few months - especially older releases.

Do not make assumptions about automatic patching or that no action is
required:
- All OS vendors have some statement about which components of their
software are affected.
- In many cases SysAdmins have automatic updates turned off.
- Automatic patches may not provide complete coverage, and even
official patches have been found to not be compatible with all
systems.
- Over the last few months Microsoft, RedHat, and other companies
have made many updates to their websites with new documentation and
manual patches to address specific environments.
- In other cases patches require a reboot (even for Linux) which is
not done automatically unless the system is configured to do so.
- Some patches are for firmware which cannot be applied
automatically.
- Some devices (Symbol, Intermec, etc) running embedded Linux,
Windows, and/or Java are never thought of for updates.
- Some operating systems will continue to report different time
settings if the application software (database!) written over them was
compiled with pre-patch libraries.
- Some OS releases are considered "retired" by the vendors who will
publish neither automatic nor manual patches. Upgrades are required.

If you have information which you believe would be helpful to the
diverse base of MV users and developers, please let me know and I will
be happy to review it for posting.

This is not a solicitation. Nebula Research and Development is not
providing services related to this event. This information is
provided as a courtesy to the Pick / MultiValue user-developer
community.

Tony Gravagno, Nebula R&D
TG@ remove.anti.spam.textNebula-RnD.com

http://remove.thisNebula-RnD.com/blog/time/
(This blog is not a definitive resource of information, please contact
your OS vendor (vendor of hardware for larger servers) to get their
latest updates.)

I just posted another blog page that concisely summarizes all of the
Microsoft pages related to this event. There aren't that many really,
it just seems like it. Some Microsoft pages are updated on an almost
daily basis - you really should have a look.
http:// removethisNebula-RnD.com/blog/cosmos/time/2007/02/dst05.html

I won't be doing a similar page for IBM, RedHat, HP, or other vendors
as it seems they have a much more limited set of products affected by
these changes and I've already published links for them. Please feel
free to post a comment on the blog if you find links that would be
helpful to our colleagues.

HTH
Tony Gravagno
TG@ removethisNebula-RnD.com
Nebula Research and Development
(sorry for the domain munging...)

Clocks just changed. Might be good to check end-user systems to
ensure theirs did too.

Good luck.
T

Tony Gravagno wrote: