RE: CPF4236: Not authorized to open member

Don,

Have you checked to see that the owning user profile still has *ALL authority 
to the physical and logical file?

Just because the owner has *ALL by default doesn't mean that it can't be 
changed.


In addition, is this a standard DDS defined logical or a logical from a SQL 
view/index?

Related question, if you do a DSPFD what do you see for the following:
Allow read operation  . . . . . . . . . . . :            Yes  
Allow write operation . . . . . . . . . . . :            Yes  
Allow update operation  . . . . . . . . . . : ALWUPD     *YES 
Allow delete operation  . . . . . . . . . . : ALWDLT     *YES 

HTH, 

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Fisher, Don
> Sent: Monday, August 29, 2005 10:46 AM
> To: 'midrange-l@xxxxxxxxxxxx'
> Subject: CPF4236: Not authorized to open member
> 
> 
> I have a logical file called LF1 over physical file PF1.  
> Both files are
> owned by profile OWNER.  The logical file is defined in PGM1 
> that is also
> owned by OWNER and uses the *OWNER profile when executed.
> 
> When PGM1 is executed, the CPF4236 message is issued and I 
> don't understand
> why.  PGM1 is in a different library than LF1 and PF1, but 
> that shouldn't
> make a difference.  Both libraries are also owned by OWNER.
> 
> Any thoughts will be greatly appreciated.
> 
> Donald R. Fisher, III
> Project Manager
> Roomstore Furniture Company
> (804) 784-7600 extension 2124
> DFisher@xxxxxxxxxxxxx
> 
> -- 
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
>