|
Sorry, I did think it strange you wouldn't know the answer. I guess I wasn't following the thread closely enough. You are right, the message file isn't available so one's hands are tied in regards to what can be done with the message information. Rick Chevalier AmeriCredit AITS (817) 525-7178 rick.chevalier@xxxxxxxxxxxxxxx -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Tuesday, January 06, 2004 8:09 AM To: RPG programming on the AS400 / iSeries Subject: RE: Error Handling for QCMDEXC That I know. But how would one programmatically determine that from seeing SQL0204 in their joblog, or perhaps a user written message file message? Yes it could be done by scanning all message files on the system for that particular message, but my argument was that getting the message data back into a 'wordy' format when all your given is the message number from the joblog and the exception data can be a bit tricky. That is why, on conditions in which the PSDS is updated, some may prefer QCMDEXC over QCAPCMD. QCAPCMD uses the error data structure http://publib.boulder.ibm.com/iseries/v5r2/ic2924/info/apis/error.htm#hdrerrcod And is missing the data available via the MSGF and MSGFLIB parameters of RCVMSG. 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? Thanks for the tip, but perhaps I've made my point, yes? Rob Berendt -- "All creatures will make merry... under pain of death." -Ming the Merciless (Flash Gordon) "Chevalier, Rick" <Rick.Chevalier@xxxxxxxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 01/06/2004 08:50 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, The SQL messages are in QSQLMSG message file. Rick Chevalier AmeriCredit AITS (817) 525-7178 rick.chevalier@xxxxxxxxxxxxxxx -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Monday, January 05, 2004 4:05 PM To: RPG programming on the AS400 / iSeries Subject: Re: Error Handling for QCMDEXC 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. _______________________________________________ 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.
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.