Re: RNF7534-Files should be closed explicitly when NOMAIN is specified onthe Control specification. -- RPG400-L

So does this boil down to just a few choices?
1 - Explicitly open and close the file all the time.

Personally, I code a subprocedure called "init" (or whatever you like)that opens all of the files. In each of the exported procedures, I codethis as the first few statements:


    init();

The init subprocedure sets an indicator to keep track of whwther the filesare open or close. If they're already open, calling init() a second timeis a no-op.


Basically, the init() procedure looks like this:

   /free
         if (FilesOpen);
            return;
         endif;

         if not %open(FILE1);
              open FILE1;
         endif;

         if not %open(FILE2);
              open FILE2;
         endif;

         if not %open(FILE3);
              open FILE3;
         endif;

         FilesOpen = *ON;
   /end-free

Like I said... every other exported subprocedure in the module calls thisone as it's first line of code. The goal is that the first call to themodule will cause the files to open. Subsequent calls won't do anything.


Then, I also have a done() procedure that closes the files:

   /free
        close *all;
        FilesOpen = *OFF;
   /end-free

In many of my service programs, this subprocedure is never called, but itstops the warning messsages from the compile. In other service programs,I'll insert code into my init() procedure that uses the CEE4RAGE() API toregister the done() procedure to be called automatically when theactivation group ends. That way, I can use it to clean up temporaryobjects, like user spaces or data queues, that wouldn't be automaticallydeleted by ending the activation group.

This way, my files are opened ONCE, not repeatedly. And they're closedONCE when the activation group ends.

2 - Use ACTGRP(*NEW) on CRTPGM and explicitly close the file to eliminate
the warning messages.  The AG will implicitly open the file.

That works, too... but I don't like to start a new activation group on acall to a service program. As far as the srvpgm is concerned, it's always"loaded forever". If the caller wants to unload it by using ACTGRP(*NEW)or RCLACTGRP, that's the caller's responsiblity, not the srvpgm. (but,that's why I often use CEE4RAGE, to ensure that if the caller does end theactivation group, everything is cleaned up nicely.)

3 - Implicitly open the file, don't worry about closing it, and ignore the
compile warning messages about close.

I never do that -- and it's not that I really care about the warningmessage, it just doesn't seem intuitive to me. There's no otherprogramming language anywhere where the programmer expects the runtime tomagically open and close the files for you, why should RPG be different?


Would setting on the LR indicator do anything?

No. LR has no impact on a NOMAIN module. (Activation groupswere created as a way of enabling LR-like behavior across multuplelanguages. I suggest forgetting about LR and other cycle-driven stuff,and use activation groups instead. But it's not worth fighting about, soplease don't turn this into a "holy war.")