I was really only referring to Monitor vs %status/%error as far as error
checking goes, not so much the deal with an error when you get it vs
avoid an error.
Kurt Anderson
Application Developer
Highsmith Inc
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
GUY_HENZA@xxxxxxxxxxxxxx
Sent: Wednesday, January 09, 2008 12:01 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Checking for dupe key on WRITE
As "a matter of style", why not SETLL and not do the write if equal or
found?
Regards,
Guy
"Kurt Anderson"
<kjanderson@highsm To: "RPG
programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
ith.com> cc:
Sent by: Subject: RE: Checking
for dupe key on WRITE
rpg400-l-bounces@m
idrange.com
01/09/2008 12:55
PM
Please respond to
RPG programming on
the AS400 /
iSeries
Just a matter of style, but I tend to prefer something like this:
Monitor;
Write Rec;
On-Error DuplicateKey;
// do something
EndMon;
Of course you don't need to specify the status with the On-Error opcode
if you'd rather have a catch-all.
Kurt Anderson
Application Developer
Highsmith Inc
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, January 09, 2008 10:46 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Checking for dupe key on WRITE
ILE RPG Reference manual available at InfoCenter.
D NoError C 0
D EndOfFile C 11
D RecordNotFound C 12
D DuplicateKey C 1021
D ReferentialErr C 1022
D TriggerErrBef C 1023
D TriggerErrAft C 1024
D YouAreOld C 1031
D FileClosed C 1211
D FileOpen C 1215
D ImpOpenCloseEr C 1216
D ExpOpenCloseEr C 1217
D RecAlreadyLock C 1218
D UpdBeforeRead C 1221
D RefErrOnAlloc C 1222
D PermIOErr C 1251
D JobEndingCtl C 1282
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
"Thompson, Glenn" <gthompson@xxxxxxxxxxxxx> Sent by:
rpg400-l-bounces@xxxxxxxxxxxx
01/09/2008 11:34 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
To
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx> cc
Subject
RE: Checking for dupe key on WRITE
Ken,
Where can I find listing of "descriptive errors"?
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Ken Slaugh
Sent: Wednesday, January 09, 2008 10:30 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Checking for dupe key on WRITE
Here's how I checked for the Dup using %ERROR and Program Status DS...
d SDS
d qExceptD 91 170
* Check for duplicate key detected
c if %subst(qExceptD:1:13)
c = 'Duplicate key'
- Ken
(707) 795-1512 x118
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Thompson, Glenn
Sent: Wednesday, January 09, 2008 8:23 AM
To: RPG programming on the AS400 / iSeries
Subject: Checking for dupe key on WRITE
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
________________________________________________________________________
_____
Scanned by IBM Email Security Management Services powered by
MessageLabs. For more information please contact
mailto:smtpalerts@xxxxxxxxxx
________________________________________________________________________
_____
--
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.
--
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.
--
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.
--
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.
--
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.
midrange.com
