×
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.
On 22 May 2012 12:34, Scott Klement wrote:
By default, an open data path (ODP) is _not_ shared across two
programs. This can be changed by specifying SHARE(*YES) on the
CRTPF/CRTLF commands, or on an override: OVRDBF SHARE(*YES)
<<SNIP>>
But, if someone has changed the file (either via
CRTPF/CHGPF/CRTLF/CHGLF or OVRDBF) to SHARE(*YES), this is causing
your grief. <<SNIP>>
FWiW the SHARE() parameter on those CRTxF commands is just a proxy
for the effective ADDPFM or ADDLFM that is performed for the member
added, whenever anything other than MBR(*NONE) is specified. The SHARE
specification is not a file-level setting that is adopted by a member
created for that database *FILE. Instead, the attribute is established
by whatever was specified on the ADDxFM or CHGxFM [CHGLFM or CHGPFM] for
that command's SHARE() parameter. The CHGxF commands would effect
setting the SHARE specification for all members of a database *FILE.
Regards, Chuck
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.
midrange.com
