RE: Error Handling for QCMDEXC

[rob@xxxxxxxxx]

I submitted a DCR asking for ERRC0300 with the message file name and the 
message file library name.

Rob Berendt
-- 
"All creatures will make merry... under pain of death."
-Ming the Merciless (Flash Gordon)




Scott Klement <klemscot@xxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
01/06/2004 11:03 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: Error Handling for QCMDEXC







Rob,

I agree that missing the library/name of the message file is major flaw in
the API error structure, and has caused me grief many times in the past!

I don't think that the MSG or SECLVL data are needed, however.  Those two
items would take up a significant amount of memory, and for every API to
have to add code to populate them seems a little silly when we can easily
retrieve them w/QMHRTVM if we want them -- or simply send a program
message to our caller.

But in order to really use the API error structure with either QMHRTVM or
with QMHSNDPM, we REALLY need that message file name and library!!


On Tue, 6 Jan 2004 rob@xxxxxxxxx wrote:
>
> Missing these makes it hard to take the exception data and parse
> it down into meaningful information.  Perhaps I need to make a DCR to 
add
> another structure that also contains the following of RCVMSG:  MSGF,
> MSGFLIB, MSG, SECLVL.  What do y'all think?
>