Re: Update on Closed File Error... I don't think so!

It took a while for what you said to sink in.
WHIRRRR - CLICK
that's the penny dropping


Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxxxxx
P:(631) 244-2000 ext. 5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill

rpg400-l-bounces@xxxxxxxxxxxx wrote on 07/22/2008 11:52:34 AM:

Alan Shore wrote:

Actually you don't need to use a flag. Try this.
if not %open(file);
open file;
endif;

// do stuff

if %open(file);
close file;
endif;

We tried that initially ... but it burned us big time.

We tend to call procedures from within procedures ... and one
procedure might open a a file that another procedure needs.

If the second procedure explicitly closes the file, then the calling
procedure will have a file closed it doesn't expect.

Setting the flag makes sure that we ONLY close the file if we
actually opened it.

david

--
IBM i on Power - For when you can't afford to be out of business
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing

list

To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.