RE: explicit close

Patrick Conner wrote:

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

It would be a Very Good Idea if you did.  See below...

>Why should I explicit
>close the files in the functions?

Because the file will stay open as long as the activation group you're using
stays alive.  This means that if you fire up your program at 8 AM, set on LR
at 8:05 and do other work all day then come back to your program at 16:00
the file will still be open.  Check the oft referenced Redbook "Who knew you
could do that with RPG?"  http://www.as400.ibm.com  Follow the library link.

I would say that typical I/O functions have at least 3 sub-functions: Open,
Get (or Put) and Close.  This way the caller is in control and there is no
"secret" open or "cleanup" done by the I/O function.  Lurkers should take
the opportunity to add their comments to this - especially contradictory
ones!  There is no one "right" way, there are only better or worse choices
for your application.  The more ideas you hear about, the better you can
decide for yourself.

Buck Calabro
Aptis; Albany, NY
"We are what we repeatedly do.
 Excellence, then, is not an act, but a habit." --Aristotle


Billing Concepts Corp., a NASDAQ Listed Company, Symbol: BILL
+---
| 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
+---