I have seen share(*Yes) used on display files when using multiple
modules for a single program as well as for multiple programs that call
each other. It is used to pass data back and forth rather than put them
in parameters or the LDA. (not my design - I just deal with it)
Sharon Wintermute
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck
Sent: Wednesday, March 03, 2010 2:04 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: ovrdbf SHARE parameter
On 3/3/2010 10:41 AM, David FOXWELL wrote:
Vern, Sharon,
Your 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?
It sounds like someone does not understand the purpose of SHARE(*YES)
but I cast no aspersions. SHARE(*YES) is one of those things that never
saw much use except among us old timers working on old, slow machines.
I haven't used it in many years now, and certainly never with SQL. Is
your SQL reference using system naming or SQL naming? I would not be
surprised if that made a difference. Although I'm now curious, I
haven't the time to mock up the example code to test the different
scenarios.
--buck
midrange.com
