× 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.




On 21/03/2008, at 12:12 AM, Arthur.Marino@xxxxxxxxxxxxxxxx wrote:


What if 2 procs in the same service pgm use the same file. If both of the
procs are invoked by the calling pgm, will the 2nd proc recognize that the
common file was already opened by the 1st (if %open)? If so, won't there
be a problem if the 2nd proc closes that file while the 1st, thinking it's
open, tries to access it again? The net of it is, I guess, are the file
opens scoped to the module (*srvpgm) or to the interior procs that opened
them?

Files (prior to VRM610) are scoped to the MODULE. If your procedures are in the same module then %OPEN will work as you expect. If they are in separate modules (but the same service program) then they won't. Doing a lazy open is fine ( if not(%open(file)) ) in all procedures but once open they should be left open until either the job ends, the caller explicitly closes (via a cleanup() procedure your service program provides), or the activation group ends.


Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.