|
*EXECUTE rights is one of those things added later in the AS/400's life. And frankly, I've never quite grasped the reason for it, although I guess I know one now (grin). IMHO, assigning *USE rights to a Database File is the way to go generally to assign "read-only" rights to a file. I'm not sure why someone would revoke *EXECUTE rights which gives slightly less than *USE rights. I can't see why anyone would try to hide a file from a library search, but assuming you know it's there, you would have sufficient data rightas to get at it. Odd ... Bill -----Original Message----- From: Terry Richardson [mailto:terry-sssc@xxxxxxxxxxxx] Sent: Tuesday, July 18, 2006 9:20 AM To: 'Websphere Development Studio Client for iSeries' Subject: Re: [WDSCI-L] Object authority issue Okay - That is what I have observed. I would also like to know if this is 'working as designed' or is a bug. Maybe I'll fire off a note to George Farr... Thanks for all your input!
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.