|
On 28/07/2005, at 9:53 PM, Vernon Hamberg wrote:
Of course, there's always more than one way to do it (the PERL motto - TMTOWTDI).
True. There's the RIGHT way and then there are the others.
When using CPF0000, I like using, in the global handler, the message handling APIs to get the recent diagnostics, as well as resending the last exception. This is cleaner than doing a bunch of RCVMSG commands. It uses QMHMOVPM & QMHRSNEM to do the job - here's some sample code, based on a "using APIs" book--
That is essentially what my STDERR command does but I wrote it before the APIs you mention became available. It does everything with CL commands and it doesn't move diagnostic messages. It could but I've never seen the point in moving all the error messages from one program queue to another program queue higher in the stack. Resending the escape message makes sense but not the diagnostic messages. If you need to see those they are available via F10 from the second-level display of the escape message.
I published the code to STDERR years ago so it is probably in the archives somewhere.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.
midrange.com
