|
Hi: On our AS/400 (V5R2) the scheduled change via two CL programs didn't work because the code I borrowed didn't have the system values in the right format. I checked from home Sunday and fixed it interactively. Everything since has been cheerfully ignorant of the change (i.e., it's all working). On the Windows side of things, nightmarish. NOT ONE server or PC correctly updated to Central Daylight Time, in spite of us having tolerated days of productivity-crushing update reboots. This includes W2K Pro, WinXP, and Win2003 Server machines. The access security system was still old time, as were the Notes applications servers ... the list goes on. The main network server was also still on Central Standard. When I reset its clock manually it seemed OK, but about an hour later it added yet ANOTHER hour, putting us either on Eastern Daylight or Atlantic Standard (although the time zone still said Central US). The network admin is still fighting with that, and some other bizarre fallout such as the backup server skipping all but one of the network weekend full backup jobs (Symantec Backup Exec, but not idea yet if the software or the O/S was at fault). Ironically, when I got here this morning it appeared that our phone system digital switch was also a victim of Y2Klock. But no, that was just a power supply. Once the tech got out of bed and drove here, the hardware replacement took 20 seconds. Darrell Darrell A. Martin - 630-754-2141 Manager, Computer Operations dmartin@xxxxxxxxxxxxx midrange-l-bounces@xxxxxxxxxxxx wrote on 03/12/2007 07:42:40 AM:
How did everyone's DST change go?? Ours was pretty painless. How was everyone else's?? Joel B. Harvell Food Lion, LLC (704) 633-8250 x2709 jbharvell@xxxxxxxxxxxx
**************************************************************************
This electronic message may contain confidential or privileged
information
and is intended for the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please
notify
the sender immediately by using the e-mail address or by telephone (704-633-8250).
**************************************************************************
-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
This e-mail, including attachments, may contain information that is confidential and/or proprietary, and may only be used by the person to whom this email is addressed. If the recipient of this e-mail is not the intended recipient or an authorized agent, the reader is hereby notified that any dissemination, distribution, or copying of this e-mail is prohibited. If this e-mail has been delivered to you in error, please notify the sender by replying to this message and deleting this e-mail immediately.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.