If the first noted procedure also does the full-open and SHARE(*YES) is in effect [, scoped for future opens in the same routing step], then when the other procedure does its own open & close, the impact for full opens will be reduced. That is, /continuous/ paired open & close activity would be /shared/ instead of paired full-open & full-close.

The SHARE() parameter on OVRDBF "Specifies whether the open data path (ODP) is shared with other programs in the same routing step. When an ODP is shared, the programs accessing the file share facilities such as the file status and the buffer." Note: The SHARE() parameter on CRTPF & CRTLF applies *only* to the/when member being created; i.e. it is not a file-level specification, such that the ADDPFM & ADDLFM have their own SHARE() parameter, but there is no option SHARE(*FILE).

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 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.