Re: RPG400...a chain, a reade, no indicators...now what?

["Dennis Lovelady" <dlovelady@xxxxxxxx>]

One thing that comes to mind is:

Set a field to a value that you KNOW won't be in the file, just before the
read.
Execute the read.
Did the value change?

Another thing that comes to mind is:

Recompile the dang program WITH a %EOF test????

Dennis





"Rick Rayburn" <the400man@hotmail.com>@midrange.com on 12/19/2002 07:08:58
AM

Please respond to midrange-l@midrange.com

Sent by:    midrange-l-admin@midrange.com


To:    midrange-l@midrange.com
cc:
Subject:    Re: RPG400...a chain, a reade, no indicators...now what?


but how in debug can you test for a successfull or unsuccessful read or
chain without the indicator?






>From: "Booth Martin" <Booth@MartinVT.com>
>Reply-To: midrange-l@midrange.com
>To: <midrange-l@midrange.com>
>Subject: Re: RPG400...a chain, a reade, no indicators...now what?
>Date: Wed, 18 Dec 2002 21:50:27 -0500 (Eastern Standard Time)
>
>
>Think %EOF, not %Found.
>
>There's NO need to ask me how I learned that.
>
>
>
>---------------------------------------------------------
>Booth Martin   http://www.MartinVT.com
>Booth@MartinVT.com
>---------------------------------------------------------
>
>-------Original Message-------
>
>From: midrange-l@midrange.com
>Date: Wednesday, December 18, 2002 21:13:15
>To: midrange-l@midrange.com
>Subject: RPG400...a chain, a reade, no indicators...now what?
>
>Hello there everybody -
>
>Happy holidays to all who make this such a valuable and wonderful place to
>exchange ideas about the "best damn computing system" in the world today!
A
>question if you will:
>
>The following code should not be unusual (i think) in an RPG400 program:
>
>Dou Not % error
>Key Reade (E) File
>If %error
>(error msg sending routine)
>iter
>endif
>Enddo
>
>In RPG3 days, the "If %error" would more than likely have been a check for
>an error indicator. And if you were in a loop because of a lock, you could
>debug your way out by changing the value of the indicator to allow the
code
>to fall through. How does one handle that in the above scenario? For that
>matter, how do you view, within debug, a successful or unsuccessful chain,
>or read, that is not governed by an indicator if your debug statement
falls
>on that testing line of code (e.g. If %found (file)...)??