× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: explicit close
  • From: bmorris@xxxxxxxxxx
  • Date: Fri, 25 Aug 2000 18:29:52 -0400
  • Importance: Normal


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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.