Re: Suggested technique

[Tony Carolla <carolla@xxxxxxxxx>]

OH!  I was only looking at the svc program call.  Yes, this would work
as well.  I can eliminate the Monitor/On-Error ops also.  Thanks!


On Mon, 31 Jan 2005 11:52:08 -0600, Lim Hock-Chai
<Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote:
> Not understand the issue yet.
> 
> If there is a dup key error the program will loop and get the next number 
> again.
>         Dou        not %error(myFile)
>         eval       MO.Mmseq# = getNextMmSeq#(CI.Family# :CI.Member#)
>       Write(e) Mmorec MO
>         enddo
> 
> 
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Tony Carolla
> Sent: Monday, January 31, 2005 11:43 AM
> To: RPG programming on the AS400 / iSeries
> Subject: Re: Suggested technique
> 
> 
> I thought about this.  Unfortunately, the sequence of events could
> happen like this:
> 
> 1)  The service program is called, and the next seq#  is 5, and gets
> returned to the caller
> 2)  The user, on the phone with an irate customer, presses enter on a
> memo record
> 3)  The program performs the write op
> *** dup key
> 
> --
> 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.
> 
> 


-- 
"Enter any 11-digit prime number to continue..."