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



"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 09/11/2016 01:00:02
PM:
----- Message from Richard Schoen <Richard.Schoen@xxxxxxxxxxxxxxx>
on Sun, 11 Sep 2016 00:56:46 +0000 -----

To:

"rpg400-l@xxxxxxxxxxxx" <rpg400-l@xxxxxxxxxxxx>

Subject:

Re: Shared File Opens Between OPM and ILE Call

Nope, turned out when they converted the program from OPM to ILE,
they were compiling the code to NOT be in the same activation group.

For those who care, shared opens don't appear to carry across
activation groups.

Regards,


Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com


Actually, there should be two options: OVRSCOPE(*CALLLVL) or
OVRSCOPE(*JOB)--but either option must also specify OPNSCOPE(*JOB)

Here's the help text for *CALLLVL and *JOB:

*CALLLVL
The scope of the override is determined by the current call level.
All open operations done at a call level that is the same as or
higher than the current call level are influenced by this override.

*JOB
The scope of the override is the job in which the override occurs.

Jon and Susan wrote an excellent article on this topic about 12 years ago.
Here's a link to the relevant page:

http://www.ibmsystemsmag.com/ibmi/developer/general/The-Seven-Deadly-Sins-of-ILE/?page=2

or http://tinyurl.com/OVR-OPNSCOPE

Michael Quigley
Computer Services
The Way International
www.TheWay.org


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.