|
These modules that are left open are in an activation group. I believe that the files will be left open, until explicitly closed, until that activation group ends. Most likely, they are running in the Default activation group which isn't going to end until you sign off and end the job (is this right? Or can different jobs/signons share the same activation group?). The solution I used in this case was creating a new subprocedure in my modules called CloseXXX such as CloseCartage. This module simply closed the files if they were open and returned. I would call this at the end of my programs that used this module. Regards, Jim Langston Me transmitte sursum, Caledoni! James David Rich wrote: > > I have a program which is leaving files open after it exits. The program > consists of three modules. Each module has its own screen file and opens > a database file. The two modules which have NOMAIN in the H spec are > leaving their associated files open after the program exits. This is not > good. Aren't all files supposed to be closed when the program exits > (including files opened by various modules of a program)? > > James Rich > james@eaerich.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-2024 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.