Re: Error Handling for QCMDEXC

[rob@xxxxxxxxx]

thanks for the clarification.  The data is there in QCAPCMD.  However it 
involves taking the exception data from the error data structure and 
putting it back into the message (via QMHRTVM) if you want it "wordy". And 
it gets real fun if you don't know what message file to use (like for 
message SQL0204).

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




Barbara Morris <bmorris@xxxxxxxxxx> 
Sent by: rpg400-l-bounces+rob=dekko.com@xxxxxxxxxxxx
01/05/2004 04:33 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
rpg400-l@xxxxxxxxxxxx
cc

Fax to

Subject
Re: Error Handling for QCMDEXC






rob@xxxxxxxxx wrote:
> 
> Although I have an affinity for QCAPCMD, this PSDS information is the 
one
> benefit of QCMDEXC over the system() api.  As previously pointed out by
> Barbara many times.
> 

Just for the record, it's the joblog information that I think is
important.  Having some of the message text in the PSDS is nice, but a)
the PSDS information is only useful if the programmer does something
with it, and b) sometimes the interesting information is in the second
level text of the message, and that can only be seen from the joblog (or
by receiving the message).

_______________________________________________
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.