RE: %error handling

Brian,

Take a look at this article.

http://search400.techtarget.com/tip/1,289483,sid3_gci1004244,00.html

Talks about naming your constraints like ALL0021_Product_To_Category

This allows you to pull message description ALL0021 in to present to the
user.


HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx 
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Lewis
Sent: Friday, November 10, 2006 6:21 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: %error handling

I've tried to set up my files so that it's hard to insert junk into
them with a combination of uniqueness and referential integrity
constraints added by ADDPFCST and "before insert"/"before update"
trigger programs.

I made an interactive program to maintain these files. If something
goes wrong on an insert or an update, it's most likely because they
tried to add a record with a duplicate key, or one of the field values
was rejected by a trigger program. I want to show them some 
informative
message that helps them understand why it didn't work. Right 
now, that's
seeming absurdly difficult to do.

The stuff that QMHRCVPM tends to receive inside my "if 
%error" block isn't
nice enough to show the user. For example, one message says something
about a duplicate key in such and such member, but the user has no
interest in the member. Another message says that an error occurred in
a trigger program, which isn't exactly right -- the trigger 
program did
what it was supposed to.

I'm not seeing some practical way to display useful error messages. Am
I supposed to be building my own huge table of %status code messages
or something?
-- 
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.