Re: SQL function WEEK_ISO for years beyond 2039

Sample use:
D count S 10i 0
d wkdate s d
d eomdate s d
d x s 10i 0
/free
exec sql
Set Option
Naming = *Sys,
Commit = *None,
UsrPrf = *User,
DynUsrPrf = *User,
* Datfmt = *iso; *
// CloSqlCsr = *EndMod;

On Sat, Jan 4, 2025 at 6:55 AM Arco Simonse <arco400@xxxxxxxxx> wrote:

Hi Ake,

Did you follow Robs advice to set the date format to *ISO?
That should instruct the SQL precompiler to use DATE(10).

Regards,
Arco
--



Op za 4 jan. 2025 12:18 schreef <konsult@xxxxxxxxxxxxxxx>:

Thanks for the input.

I did try to set the environment value as:

ADDENVVAR ENVVAR(QIBM_QBASEYEAR) VALUE(1970) LEVEL(*SYS)

And restart the job, recompile the program and run again.

Alas same result.

The problem is that while the date variable in the program is "DATE(10)"
the
variable in the SQL structure created by the pre-compiler is DATE(8).

Thus

the problem seems unsolvable.

I guess that I will simply resign to making the program work up until

2039

(at a time where I will most definitely be retired) and send out a

warning

that if run beyond that time the calendar file will have to be maintained
manually.

/Ake/

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