|
I was on call the week of 1/1/01. We had a program that used the Julian date to check the (3 days in the future max) date entered by the operator. Apparently it had run for ten years or so without the future date being in the next year. That was the closest I came to having to fix a Y2K bug in the middle of the night that week. > -----Original Message----- > From: Leif Svalgaard [mailto:leif@leif.org] > Sent: Thursday, February 21, 2002 2:06 PM > To: midrange-l@midrange.com > Subject: Re: Month Start/Month End > > > > From: Chris Whisonant <chris.whisonant@comporium.com> > > > Just a thought, but could you CVTDAT from (say) *SYSVAL > format (02212002) > > to *JUL (yyddd), add 1 to the *JUL date, then CVTDAT back > from *JUL to > > *SYSVAL, then see if the "dd" position = "01". If so, then > the date is the > last day > > > of the month. > > > > > > Haven't tried it, but it's worth a shot. > > > > no, it would just compute tomorrow's date and may even > complain on 12/31. > > > > of course, if it is today you are checking then it would > work, except for > at the end of the year where you may get and error, but you > might monitor > for that... > > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.