|
-----Original Message-----[mailto:rpg400-l-bounces@xxxxxxxxxxxx]
From: rpg400-l-bounces@xxxxxxxxxxxx
On Behalf Of Ken Slaughto
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
do file I/O error checking with %error.do
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
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
_____list
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
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.