× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



*NOPWDCHK would be useful!

We use the default USRPRF(*USER) on our compiles. What are the
implications of compiling this particular application with USRPRF(*OWNER)?
Off the top of my head, there's nothing that would get a user to a command
line from within this program.

- Dan

On Tue, Sep 11, 2018 at 12:19 PM, Kevin Bucknum <Kevin@xxxxxxxxxxxxxxxxxxx>
wrote:

If the program is running as *OWNER and the owner of the program has
*USE for the profile you are switching to (and also when you switch
back) then you can us *NOPWDCHK and not have to know the password.

Store the user profile currently running the job.
Call QSYGETPH with new user profile and *NOPWDCHK.
Call QWTSETP with the handle from QSYSGETPH
Do your work.
Call QSYSGETPH with the stored user profile and *NOPWDCHK.
Call QWTSETP with the new handle.

Spawn was just brought up as a way possibly create a sandbox around the
job elevating authority. Data queues were also mentioned.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.