RE: File Exception/Error Subroutine - INFSR

[Dan <dbcerpg@xxxxxxxxx>]

Good style, Scott, I'll remember to use that.  Thanks.

I guess the bigger question was whether you can explicitly call the
file's INFSR subroutine and expect the same behavior as if RPG itself
called it.  I.e.:

Key chain      myfile
    if         %error(myfile)
    if         %status(myfile) = RecordLock
    ... <process retry opportunities>
    else
    Exsr       MyFile_INFSR
    endif
    endif

The whole reason for doing this is to be able to continue normal
processing after the record lock has been resolved.  Any other error,
then I want the INFSR to take over and handle the situation as if there
was no %error handling coded after the chain.

Really need to get to v5 to use the MONITOR opcode.  But until then...

TIA, Dan

--- Scott Mildenberger <Smildenber@washcorp.com> wrote:
> Yes, you can.  I have defined several constants in a /copy member so
> I can
> do something like:
>
> if %status(myfile) = RecordLock
> ...
> endif
>
> Scott Mildenberger
>
> > -----Original Message-----
> > From: Dan [mailto:dbcerpg@yahoo.com]
> > Sent: Tuesday, November 26, 2002 8:59 AM
> > To: rpg400-l@midrange.com
> > Subject: RE: File Exception/Error Subroutine - INFSR
> >
> >
> >
> > Carrying this a little further.  Let's say there's a chain /
> > read on an
> > update file, and there's a record lock condition.  Can I check
> %status
> > right after the chain or read and, if %status = 1218, process
> > option_to_retry routine; otherwise EXSR the file's INFSR?

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com