Very good point, Paul, thanks. That happened to creep in because I copied the code from an ISPF application...
I've never heard of leap seconds! Leap years, but not leap seconds. Is this something with time zones in Australia? Lindy -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Paul Gilmartin Sent: Wednesday, October 25, 2006 6:43 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Why would Rexx Date/Time be different from ASCBEWST Date/Time? In a recent note, Lindy Mayfield said: > Date: Wed, 25 Oct 2006 16:47:00 +0200 > > date=DATE(U) > time=TIME() > ... > Say 'Rexx Date/Time:' date time > Do not do this. There's a (small) chance that the date will change between the two calls, and the result printed will be in error by 24 hours; a nasty bug for being almost impossible to reproduce. Rather, do: Say 'Rexx Date/Time:' DATE(U) TIME() I recognize this is a one-off, but as mentioned recently in these lists, one-time code has a nasty habit of creeping into production, as do careless habits practiced in one-time code. -- 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
