|
James, There is usually no reason to close the file, if there is, you can reclaim the activation group, code a close routine that is explicitly called, or register a cleanup that calls a procedure in the module to close the file. The main reason you would need to close the file is if you are sharing access paths and need to open the file for update. In this case I would not share access paths of files open for update. This may sound like extra overhead, but it won't be if you consolidate your file access for a file into a single, shared module. David Morris >>> james@dansfoods.com 03/02/00 09:25AM >>> On Wed, 1 Mar 2000 pcunnane@learningco.com wrote: > Code the file with USROPN. In the procedure: > > if not %open(CUSTMAST) > open CUSTMAST > endif > > You will want a cleanup routine to explicitly close the file, or allow > it to be closed when the activation group ends. Ah - there's the rub. How do I code it so that the file is opened on first invocation (that is what you have above) and closed when the calling program exits (*not* when the procedure exits). James Rich james@dansfoods.com +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.