|
That's how I would do it...add *MONTHS(1). And since they're true dates, you don't need to worry about the year. On 11/9/06, Wayne McAlpine <wayne.mcalpine@xxxxxxxxxxxxxxxxx> wrote:
From the RPG manual: When adding a duration in months to a date, the general rule is that the month portion is increased by the number of months in the duration, and the day portion is unchanged. The exception to this is when the resulting day portion would exceed the actual number of days in the resulting month. In this case, the resulting day portion is adjusted to the actual month end date. The following examples (which assume a *YMD format) illustrate this point. '98/05/30' ADDDUR 1:*MONTH results in '98/06/30' The resulting month portion has been increased by 1; the day portion is unchanged. '98/05/31' ADDDUR 1:*MONTH results in '98/06/30' The resulting month portion has been increased by 1; the resulting day portion has been adjusted because June has only 30 days.Similar results occur when adding a year duration. For example, adding one year to '92/02/29' results in '93/02/28', an adjusted value since the resulting year is not a leap year. AGlauser@xxxxxxxxxxxx wrote: > Alan Shore wrote on 09/11/2006 02:09:09 PM: > > > I am assuming that you have a file with this data on, and in its > simplest >> form is >> >> Review date >> Employee number >> Employee last name >> Employee first name >> Employee middle initial >> Employee supervisor. > > If Alan is correct, but you want to notify managers automatically of > impending reviews, you can do something along these lines: > > position the file so you don't read any records < 11 months old > > for each record; > if ( %diff( reviewDate + %years(1) : today : *days) <= 30); > sendNotice(); > endif; > endfor; > > I don't know if using '30 days' instead of '1 month' works for you. If > not, it might get a bit complicated. You will have to decide what one > month before March 31 is. Is it February 28? March 1? Something else? > > HTH, > Adam > > ##################################################################################### > Attention: > The above message and/or attachment(s) is private and confidential and is intended > only for the people for which it is addressed. If you are not named in the address > fields, ignore the contents and delete all the material. Thank you. Have a nice day. > > For more information on email virus scanning, security and content > management, please contact administrator@xxxxxxxxxxxx > ##################################################################################### -- 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.