> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Edward Jaffe > Sent: Thursday, May 11, 2006 1:50 PM > To: [email protected] > Subject: Re: TOD clock discussion. > > > McKown, John wrote: > > I guess my question is: Why does IBM and other software > vendor depend on > > the TOD clock not changing "drastically" and never, ever, "going > > backwards"? > > Ours is not to reason why. The architecture (PoOps) describes the > behavior of the TOD clock and other facilities. These behaviors were > decided upon a long, long time ago and applications depend on > them. You > can no more allow the TOD to go backwards than you can allow a CDS > instruction to not serialize in some cases. That's how it > works because > it's documented that way! > > > How would you address this "complaint". Without spending any > > money (gilt, lucre, dinero, ...) > > > > Issue a daily SET TIMEZONE= command to adjust the local time > as necessary. > > -- > Edward E Jaffe
Well, we are planning on doing a T CLOCK=. In what way would a T TIMEZONE= be better? Oh, and just to myself, I don't really like this too very much. But then, I'm just an old grump. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. ---------------------------------------------------------------------- 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
