|
-----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Joe Pluta P Strerror B D Pi 128a Varying D sys_errno Pr * ExtProc( '__errno' ) D sys_strerror Pr * ExtProc( 'strerror' ) D 10i 0 Value D Error s 10i 0 Based( pError ) NoOpt C Eval pError = sys_errno C Return %Str( sys_strerror( Error )) Thanks Joe and Simon. The use of NoOpt on the Error based integer is interesting. The manual says "Specifying NOOPT ensures that the content of the data item is the latest assigned value. This may be necessary for those fields whose values are used in exception handling." I would think that the use of NOOPT here is overkill since once this exception handling code starts to run the exception has, by definition, already occurred. The NOOPT is only needed within the code that the exception has jumped over as the unmonitored exception falls down the call stack. Steve
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.