|
Ed Fishel wrote: > First, the Create Program (QPRCRTPG) API is shipped with public *USE > authority. Second, adopting QSYS authority just to guarantee access to a > few commands and APIs is adopting more authority than is needed. Actually, while that may be true at present (I haven't had reason to check the public authority of QPRCRTPG in quite a few years), but at the time I re-implemented QuestView's program creation function to use QPRCRTPG instead of a hacked privileged instruction (i.e., V2R2 through V3R2), it was shipped with public *EXCLUDE. I was there. My memory may be playing tricks on me, but I think it's even documented as such in the V2R3 API manual. It was either make that one program *OWNER with an owner of QSYS, make it *OWNER with an owner of QSECOFR (which seemed far worse), require users to change the public authority of QPRCRTPG, or make VIEW program creation (which is something we strongly encourage QuestView users to use) something that can only be used from privileged accounts. -- 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-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.
midrange.com
