RE: Duplicate Record Monitoring

["Lapeyre, Francis" <FLAPEYRE@xxxxxxxx>]

It's a snippet. However, I've never had any error other than a 1021 on that
file. If it should go into an endless loop, we would know about it; the
system will page us when this program runs over 1 hour. 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of rob@xxxxxxxxx
Sent: Monday, February 27, 2006 10:20 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Duplicate Record Monitoring

Is this just a snippet?  Because if it was any other error, wouldn't your
DOU be a perpetual loop?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Lapeyre, Francis" <FLAPEYRE@xxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
02/27/2006 11:12 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
"'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: Duplicate Record Monitoring






Yep. I always check %status:

     C                   Eval      Cnhunq = 1

 

      ** Add to CNHUNQ to avoid possible duplicate records in ARCNHL2

     C                   Dou       Not %ERROR

     C                   Write(E)  Cnh

     C                   If        %ERROR And %STATUS(Arcnh) = 01021
01021=Duplicate Key
     C                   Eval      Cnhunq = Cnhunq + 1

     C                   Endif

     C                   Enddo 

Francis Lapeyre
IS Dept. Programmer/Analyst
Stewart Enterprises, Inc.
E-mail: flapeyre@xxxxxxxx 

 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of rob@xxxxxxxxx
Sent: Monday, February 27, 2006 9:27 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Duplicate Record Monitoring

I disagree with "assuming" error is because of a duplicate error.  The 
error
could be:
- trigger threw an error because it didn't like it.
- referential constraint violation
- any of the numerous other errors possible.
Look at the list of error codes possible.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Booth Martin <booth@xxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
02/24/2006 04:50 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
cc

Fax to

Subject
Re: Duplicate Record Monitoring






RPG or CL?

This is the RPG list so i expect that is the answer you want?

Look at the idea of using %error.

C     write   newrecord
C     if      %error
C     update  newrecord
C     endif

This may not be enough information for your needs, but %error is very 
useful.


Mike Wills wrote:
> I am working on a system that could potentially have a duplicate record. 

I
> plan on doing a monitor on the write to monitor for the error. Is there 
a
> list somewhere of error codes so I know what to monitor for?
> 
> --
> Mike Wills
> koldark@xxxxxxxxx
> http://mikewills.name
> http://theriverbendpodcast.com
> 
> "There are 10 types of people in the world: those who understand binary, 

and
> those who don't." -Unknown