Re: explicit close

[Jim Langston <jlangston@xxxxxxxxxxxxxxxx>]

Hmm... I guess if you purposely did not want to close the file in any of your
functions I would probably do a

 *We do not close the files in this directory.  Here we prevent the compile 
error.
C                  If             1 = 2
C                  CLOSE   Somefile
C                  EndIf

Think that would be a good idea?  It should be fairly self documenting also.

Of course, I would only do that if the warning were level 10 or higher, if it's 
level 0
I would just ignore it.  I just make sure I never get any warnings in my 
compiles over
a severity of 0.

This comes from following a programmer who normally had ever level 20's all 
over the
place, and some times even a 30 or so (he must have had his settings set for 40 
or something,
otherwise I have no idea how a program would even compile with those high 
severity error
levels).

Regards,

Jim Langston

bmorris@ca.ibm.com wrote:

> >Date: Fri, 25 Aug 2000 12:00:20 -0400
> >From: Contractor1@Parkdalemills.com
> >
> >When I compile a procedure I see a compile warning stating that a file
> >should be explicitly closed when NOMAIN is specified. Do I have to use
> >USROPN on all functions to open and close the files? Why should I explicit
> >close the files in the functions?
>
> The compiler doesn't want you to close the files in all the functions,
> it's just suspicious if it doesn't find a CLOSE in *any* function.  Since
> there's no way for files to get closed in a NOMAIN module other than with
> a CLOSE operation, the compiler thinks you might have forgotten to code a
> CLOSE for the file (well, it's really me who thinks it; I put that warning
> message in the compiler).
>
> If you might want to close the files at some point in your application,
> code a "cleanup" function that does a CLOSE *ALL (and UNLOCK *DTAARA
> if you keep data areas locked).
>
> Barbara Morris, IBM Toronto Lab, RPG Compiler Development
>
> +---
> | 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
> +---

+---
| 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
+---