AW: declaring a file local to a sub-procedure

Hi,

This now brings up an additional question, since this works along the same

way as a USROPN, how much additional overhead does this generate? I mean,
if you include a file locally to a procedure and that procedure is invoked
for every order, the overhead for opening and closing that file could be
huge.....

Or does IBM preload the file so the overhead is lower on subsequent opens?

Local files are only user opened per default. It is also possible to open a
local file only with the first call and let it open for all subsequent calls
(until it will be explicitly closed. Just add the key word STATIC into the
local F-Specs. (Static is not allowed for global F-Specs)
In this way it works like any global files that are not user controlled
opened.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"


-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Doug Palme
Gesendet: Tuesday, 29. September 2009 20:13
An: RPG programming on the IBM i / System i
Betreff: Re: declaring a file local to a sub-procedure

This now brings up an additional question, since this works along the same
way as a USROPN, how much additional overhead does this generate? I mean,
if you include a file locally to a procedure and that procedure is invoked
for every order, the overhead for opening and closing that file could be
huge.....

Or does IBM preload the file so the overhead is lower on subsequent opens?