|
Al Barsa wrote: > > There are very valid reasons to specify USRPRF(*OWNER). For example: I > want a user to be able to add a member to a file, but I don't want *PUBLIC > to have either that authority in their profile or to the file. There are also very valid reasons for commercial products to be shipped not only with USRPRF(*OWNER), but with QSYS as the owner. Case in point, QuestView (and its younger sister, ThinView) both call the Create Program API, which is normally owned by QSYS with PUBLIC *EXCLUDE. If our products didn't ship with the programs that call the API set up that way, NOBODY without near-QSECOFR-equivalent authorities would be able to create VIEW programs. -- James H. H. Lampert Professional Dilettante http://www.hb.quik.com/jamesl http://members.hostedscripts.com/antispam.html http://www.thehungersite.com Help America's Passenger Trains. http://www.saveamtrak.org Read My Lips: No More Atrocities!
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
midrange.com
