×
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.
I thought I was properly taking care of opening and closing files in my
service programs by using a globally-defined flag to record whether the
service program needed to open a given file. Then, when the service pgm
proc was invoked at end-of-job in the main program, it would close only
those files that it had opened (not any that were already open when it was
initially invoked).
Today, I was testing a program that opened a file before the service pgm
proc was initially invoked. In debug, I was surprised to see that the proc
decided that this file was NOT open, so it opened it. When I looked at my
job's open files, I saw the open file twice. And both were in the same
Activation Group (QILE).
Since I'm apparently wrong about file opens/closes in a service program,
can someone enlighten me? Thank you.
Arthur J. Marino
Southern Container Corporation
(631) 297 - 2276
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
