RE: Access rights to system files

V5R1. *PUBLIC is Read only, but DSPPFM ran okay against it.

As for menus, to the best of my recollection any time I wanted to change a
menu for any reason I had to get everyone off of it. In fact, ofttimes even
if one drilled down from the menu to another menu, I know I've had issues
trying to compile it.

Jerry C. Adams
IBM i Programmer/Analyst
"He has Van Gogh's ear for music." -Billy Wilder
--
A&K Wholesale
Murfreesboro, TN
615-867-5070

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Friday, June 03, 2011 12:57 PM
To: Midrange Systems Technical Discussion
Subject: Access rights to system files

Working with IBM on a related issue, I determined that the *PUBLIC
access for QADBXREF (and probably a bunch of other files) is set to an
unusual configuration: the only access granted is Data Read authority.
A standard *USE setting has both Data Read and Execute rights as well as
Object Operational rights. Testing indicates that the latter
(Operational) rights are required in order to execute SQL against the file.

My question is two-fold:

1. Is this the same setting others see on their systems? *PUBLIC
having ONLY data read rights, with no object rights whatsover?

2. What does this setting mean? I can't even do a DSPPFM on the file.
So why give the data read rights as all? This isn't the only file like
this - other physical files in QSYS have similar settings. (Although
interesingly enough logicals over those same physicals are accessible.)

And as a side comment, has it always been the case that you can't grant
someone *USE access to a menu if someone else is using it? That seems a
little bit finicky, especially for the MAIN menu.