×
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.
David FOXWELL wrote:
<<SNIP>> examples concern a file that stays open between
different calls from different programs, I think. In my case the
file is overridden with share(*yes) then RPG1 processes the file
as a primary file, then RPG2 does the same. So I think that the
share parameter has no effect here?
Depending on the full meaning of the open\process "as a primary
file" and the scope of the override, there may be the effect that
the second program shares the open of the first. That is, if the
first program does not close the file upon return and the scoping of
the override was applicable for that program as the first open, then
the second open could be a shared open with compatible options [and
if the second program was not coded as a SHARE(NO) open; by whatever
means that open option would\might be enabled in RPG]. If by
definition the processing a"s a primary file" will close the opened
file, then even if the first open allowed for sharing [e.g. due to
the override], then the next open would need to be a full open
[although that open may then enable sharing by the next open; e.g.
due to the override].
Regards, Chuck
This mailing list archive is Copyright 1997-2025 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
