Re: RETEXCPD -- MI400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

On Thursday, January 22, 2004, at 12:32 PM, James H H Lampert wrote:

And if an exception description is declared thusly: DCL EXCM * EXCID(H'504B') BP(CPF504BH) CV('CPF'); and nothing is ever done to modify its behavior (which makes sense, since it doesn't have a name to use in a MODEXCPD statement), then what would be the state of that bit?

I do not know with certainty but my guess would be that it is on by default. I base that on the fact that the exception data is always available to the Process Default Error Handler. This suggests that the exception data is always available (presuming an exception has exception data because some do not) and that the flag simply stops it being retrieved in a particular invocation.

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  / \
--------------------------------------------------------------------

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.