Re: SQL function WEEK_ISO for years beyond 2039

Arco,
I still think it is his date format. He should switch to *ISO.
I'm at 7.5 with recent PTF's and I changed the spread way out and no
problems if I use *ISO. If I use *MDY it goes ill with
values *week_iso*(*current date* + *69* years + *3* months); *-- returns 13
with *ISO, +++++ with *MDY*

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

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>:

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/

--

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.