> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Gibney, Dave > Sent: Saturday, April 11, 2009 6:20 PM > To: [email protected] > Subject: Re: "New" TOD > > Please explain to me where future TOD/ETOD values are needed in > application code. Especially business applications. I'm fairly sure > that it's a rare application that stores future date/time values in > TOD format. > > Please understand, I'm not talking about log timestamps, even > transaction logs. But, I have a hard time envisioning the need to > evaluate or compare or most especially store a TOD format much more > than 24 hours ahead of now.
Just the examples of which I am aware: 30-year mortgages, 30-year Treasury Bills, 50-year municipal sewer bonds... I'm not saying that dates for tracking/calculating information about such instruments are necessarily stored in (E)TOD format, but it is not unreasonable to want to do so (e.g., for interest calculations which often require number-of-days-between to compute interest due). In other words, these are *possible* uses for real-world business applications. Peter This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- 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
