Re: Global files, local files, static, usropn - which is best in a service pgm

Well a having local file means that the same file can be used multiple times in the same module - each time with a different cursor.

If that is not desirable then there's not a lot of benefit that I can think of in having local files defined as static vs a global definition.

One option not mentioned in your post that I have found useful is in using the ability to pass a file as a parm. That way the caller gets to "own" a unique cursor while still maintaining the separation of the file handling logic.


On 2013-10-23, at 9:23 AM, Jack Prucha <Jack.Prucha@xxxxxxx> wrote:

We've recently installed 7.1 (jumped over 6.1) and now I have choices. I've created a service program with two subprocedures, each accessing a different file. As was previously my custom, the F specs are global, before the subprocedures, with usropn specified. The subprocedure will be called from batch, interactive and probably a web stored procedure so I don't want a bunch of file opens and closes (could be 1,000s when called from batch) happening automatically. I usually check for %open in the subprocedure and have the calling pgm call one last time to close *all files. Before starting I read a nice article in July, 2013 IBM Systems Mag by Jon and Susan (Thx!) that explained new methods of global and local file definitions and controlling opening and closing files.

Now I'm confused. Are there real advantages to local files defined perhaps with static over global files with usropn controlling opens/closes? Or is just a preference?

TIA
Jack

This email, including any documents, files, or previous email messages attached to it, has been sent from an email account of College Foundation Inc., (CFI) and may contain confidential, proprietary, or legally privileged information belonging to CFI. If you are not the intended recipient, any dissemination, distribution, or copying of this email or its attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender by email and destroy the original email and any attachments.
--
This is the RPG programming on the IBM i (AS/400 and 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.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com