RE: Bug in IBM Date Routies %month

Exactly - which is why our customers' due dates only fall between the 1st
and the 28th. When a payment gets posted, we advance the due date by 1
month. Easier that way.


Francis 



-----Original Message-----
From: rpg400-l-bounces+flapeyre=stei.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+flapeyre=stei.com@xxxxxxxxxxxx] On Behalf Of Peter
Dow (ML)
Sent: Monday, March 27, 2006 3:23 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Bug in IBM Date Routies %month

Hi Praveen,

Actually, that's not a bug, it's a problem with intermediate values.  
When you add 1 month to 2006-01-31, what do you get?  2006-02-31 is not a
valid date; instead you get 2006-02-28 (see the manual).  When you then add
1 month to that, you get 2006-03-28.  Date arithmetic is tricky...

hth,

Peter Dow
Dow Software Services, Inc.
909 793-9050

praveen gunda wrote:
> I found the following bug with IBM Date rountines... Was there a fix 
> for this?
>
>
>      Ddate1            s               d   datfmt(*ymd)
>       /Free
>        cymd = 20060131;
>        date1 = %date(cymd:*ISO);
>        dsply %char( (date1+%months(2)):*iso );
>        dsply %char( (date1+%months(1)+%months(1)) :*iso);
>      /End-Free
>
>
> Heres' the output:
>
>  DSPLY  2006-03-31
>  DSPLY  2006-03-28
>
> Shouldn't it be 2006-03-31 both the times.
>   

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.