Re: SQL function WEEK_ISO for years beyond 2039

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

What kind of date is DATE(10)? I don't know anywhere that we specify the 
DATE type like this - it seems to be an array, meant to include the 
separators. I'm just guessing.

I do see that the RPG Reference says the length of the various 
4-digit-year options is 10 - we specify things like DATE(*ISO) and we 
get something that is 10 characters long when converted to CHAR.

So I'm kind confused!

Cheers
Vern

On 1/4/2025 5:54 AM, Arco Simonse 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/