What about SMTP? Doesn't it still require the TIMEZONE parameter in the conf member to be changed twice a year? It doesn't require to be down an hour, but it is still a change that must be remembered.
Craig -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jon Brock Sent: Wednesday, October 26, 2005 1:07 PM To: [email protected] Subject: Re: Time change this weekend. Standard answer: It depends. If your OS and systems software is up to date and you have your OS configured to run off of GMT and an offset, there is probably no need to shut the system down. If you are back-level on things like CICS, DB2, etc., then you might need to in order to keep things like database log timestamps from being out of sync. Jon <snip> I am new to this company here and one of the things they do is to shut the system down on the fall time change and wait one hour before they bring the system back up. Outside of scheduler issues, is there any reason to do this? One that keeps coming up is the timestamp on VSAM files being an issue. Some questions. One does anyone else do this and if so why? Second, is there real reason why this should happen, if so what are they? Or are they just working off one bad past experience. </snip> ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
