Re: CRTLF - Share open data path, set to *YES - results in CPF4123 Open options ignored for shared open of member CDNFCPL0

Paul,

While it is possible that it will work OK, it depends on what you're doing. If you're calling another program that uses the same file the file cursor might get moved, which the caller might not expect. This would produce your classic "unexpected results". I've always used it via an override; I think it's too dangerous to allow it as a default.

-mark

On 10/6/2014 4:33 PM, Steinmetz, Paul wrote:

3rd Party application had me re-create some LF during a PTF process, I had share open data path set to *yes, which resulted in a CPF4123 Open options ignored for shared open of member CDNFCPL0.
Most of the apps LF are set to *NO, however, they do an OVRDBF file on 468 LF during initial log in.

The fix in this case was to change the LF share from *yes to *no.

Share *YES is better from a performance standpoint, but if the application is NOT coded for a shared open, then it MUST remain *NO, is this correct?

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/