Re: Strange problem with an _Rreadk()

[CRPence <CRPbottle@xxxxxxxxx>]

  From the quoted message, probably not of too much interest to 
you, but at least for the archives in response to some prior 
comments I made....

  FWiW I found the following docs showing that the "open feedback 
area" has a "file was opened shareable" indicator.  Thus code could 
review the open feedback details after the open, and issue an error 
that a shared open is not supported for that file [within that 
application].
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/dm/rbal3feedb.htm

Regards, Chuck

James H. H. Lampert wrote:
> CRPence wrote:
>
> > As alluded in my prior message(s)... Since apparently the 
> > failing code has a requirement to not share, in order to 
> > function properly, then even after "correction" to the file 
> > members to again have SHARE(*NO), an override with SHARE(*YES) 
> > can still break the file I\O processing.
>
> Fortunately, the code in question *only* runs in a server job, 
> that uses a proprietary protocol, and therefore has full control
> over all overrides.