×
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.
Yes you are correct.
Our files are created with SHARE(*YES), so that is where my OVRDBF picked up the share value I didn't want.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Wednesday, May 23, 2012 3:45 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: ovrdbf scope
On 23 May 2012 13:10, Stone, Joel wrote:
For the OVRDBF command, apparently default is SHARE(*YES). <<SNIP>>
When prompting ?OVRDBF the SHARE() parameter is noticeably devoid of
any value; i.e. there is no default value.
Unless a value is explicitly specified for the "Share open data path"
(SHARE) parameter, the Common Data Management does not establish any
value to which the SHARE attribute will be overridden. Thus an
unspecified value for the SHARE attribute in an established Override to
Database File will reflect the SHARE() attribute that was established
for the database file member, when that member is opened. The value for
that attribute of a specific database file member can be [re]set using
"Share open data path" (SHARE) parameter of either the CHGPFM or CHGLFM
command.
Regards, Chuck
midrange.com
