Re: (E), %Error and *PSSR for file operations -- RPG400-L

× 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 25/04/2005, at 4:11 AM, Tony Carolla wrote:

I have conditioned the entire loop using DOU NOT %ERROR. My question is this: If a unique key error happens on the WRITE, will the control jump to my *PSSR subroutine, in spite of the (E) extender, or will it continue the loop, turning on the %ERROR bif?

The more specific overrides the more general therefore the %ERROR indicator will be turned on and control will go to the next instruction in the loop. You are effectively monitoring for errors by specifying the (E) extender. *PSSR and INFSR are invoked for unmonitored errors. Of course, nothing stops you from passing control to your *PSSR explicitly.

This behaviour is no different from what would have occurred in non-ILE RPG if an error indicator had been specified in columns 56-57 of C-spec I/O operations.

See section 3.2.3.1 in the ILE RPG Programmer's Guide for more information.

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.