It can also be used on the display file when multiple programs use the same display file and you only want one copy in memory.

Sharon Wintermute


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Wednesday, March 03, 2010 8:22 AM
To: Midrange Systems Technical Discussion
Subject: Re: ovrdbf SHARE parameter

When you want all programs you call within your job stream to use the
same ODP. This has been used for printing from the same printer file in
several programs that are each called from that CL or a program called
by the CL.

The open has to be the same kind of open - you can't share an ODP for
input only with one for update.

HTH
Vern

David FOXWELL wrote:
Apart from using OPNQRYF, when (or why) would I want to use SHARE(*YES)?


-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Luis Rodriguez
Envoyé : mercredi 3 mars 2010 14:14
À : Midrange Systems Technical Discussion
Objet : Re: ovrdbf SHARE parameter

David,

IIRC, The answer is yes. SHARE is used to share the ODP (Open
Data Path) between different programs.

HTH,

Luis Rodriguez
IBM Certified Systems Expert - eServer i5 iSeries


On Wed, Mar 3, 2010 at 4:05 AM, David FOXWELL
<David.FOXWELL@xxxxxxxxx>wrote:


Hi,

Does this parameter have any effect on a file used in an rpg by
embedded sql? I'm looking at a lot of ovrdbf in a clp that

uses this

parameter, but without the opnqryf that I'm used to see

following it.

Sometimes the calls that follow are to SQLRPGLE programs,

which is the reason for my question.

Sometimes the calls are to ordinary RPGs and there, I don't

understand

why the programmer has added share(*yes).

Scott Klement once did an article on OVRDBF. It showed the

effect of

combining these commands at different call levels and

override scopes.

Does anyone know where I might find that article?

Thanks.
--
This is the Midrange Systems Technical Discussion

(MIDRANGE-L) mailing

list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting,

please take

a moment to review the archives at
http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list To post a message email:
MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change
list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting,
please take a moment to review the archives at
http://archive.midrange.com/midrange-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.