In a recent note, Petersen, Jim said: > Date: Mon, 4 Dec 2006 17:14:59 -0500 > > How many of you (companies), especially those running SAP, run GMT Time > with NO offset so that during Daylight Savings Time, the systems don't > need to be brought down. > > We are hearing from our SAP Server folks that although DB2 Time Stamps > its logs with GMT even if you are using an offset, the records passed > back to the SAP Servers contain LOCAL time which causes problems during > Daylight Savings Time changes. > > We are getting severe pressure from our SAP folks to run the z/OS LPARs > LOCAL=GMT. > A question at least as relevant is, "How does SAP handle this problem at non-mainframe based SAP sites?"
I believe IBM did something Very Right in basing its time services on UTC (although some customers have struggled to fall in line). SAP shouldn't be allowed to drag the mainframe down to a lower level of design sophistication. If SAP needs time stamps in UTC, SAP should use the UTC form of the TIME macro, not insist on LOCAL=UTC, nor require a semiannual shutdown. Does DB2 lack a UTC function? Does SAP perversely formulate its queries to DB2 requesting local time instead of UTC? -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
