Of course, this change to 1970 as the base date means that any date with 2 digit year that was between 1940 and 1969 is now magically a century later.


Cheers
Vern


On Fri, 3 Jan, 2025 at 12:57 PM, Arco Simonse <arco400@xxxxxxxxx> wrote:


To: midrange systems technical discussion

Hi Ake,

Not to long ago I have been bitten by the same issue. There are some
limitations on IBMi for years after 2039. On release 7.5 IBM has added
support to extend to 2069.

https://www.ibm.com/docs/en/i/7.5?topic=ios-changes-1940-2039-date-range-date-formats-2-digit-year

Hope this helps.

Regards,
Arco
--

Op vr 3 jan. 2025 19:43 schreef <konsult@xxxxxxxxxxxxxxx<mailto:konsult@xxxxxxxxxxxxxxx>>:

Modernizing program that creates/updates the calendar file for a client and
many planning functions are based on week number.



I want to use the SQL "week_iso" function and found that it works pretty
well for the next 10 to 15 years.



I have as input a date field (*ISO) format and expect a zoned two digit
value in response.



As follows:

"exec sql set :weeknum = week_iso(:datum);"



The problem occurs when generation data further on in the future like dates
in the year 2040 and beyond. Then I get a RNQ0114 error with text
indication
that year cannot be beyond 2039.



I have been searching for a workaround but have yet to find one.



/Ake Olsson/

--



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 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.