Re: Checking for dupe key on WRITE

["Francis Lapeyre" <flapeyre@xxxxxxxxx>]

Here's an example form some code of ours.


// If duplicate record, add 1 to the journal sequence number and keep

// trying to write the record until no error occurs.

Dou Not %ERROR;

Tjtstp = %TIMESTAMP;

     // Get Timestamp (CYYMMDD date; hhmmss time)

     Timestamp13## = Arvtime_Timestamp13;

    Tjmdy = Date7##;

     Tjhms = Time6##;

Write(E) Gltrjlr;

If %ERROR And %STATUS(Gltrjl) = 01021;

Tjjseq = Tjjseq + 1;

Endif;

Enddo;


On Jan 9, 2008 10:22 AM, Thompson, Glenn <gthompson@xxxxxxxxxxxxx> wrote:

> I'm trying to get away from indicators.  I'm using %eof now and want to
> do file I/O error checking with %error.
>
>
>
>
>
> When I perform a write and a record exists I'm assuming I'll check for
> %error.  How do I determine exactly what error I'm encountering?  How do
> I know if it's a duplicate record or some other error?
>
>
>
>
>
> Glenn Thompson
>
> Senior Analyst
>
>
>
>
>
>
> --
> 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.