Yes - those are two of the API's that you can use to change current user. jte -- John Earl | Chief Technology Officer The PowerTech Group 19426 68th Ave. S Seattle, WA 98032 (253) 872-7788 ext. 302 john.earl@xxxxxxxxxxxxx www.powertech.com This email message and any attachments are intended only for the use of the intended recipients and may contain information that is privileged and confidential. If you are not the intended recipient, any dissemination, distribution, or copying is strictly prohibited. If you received this email message in error, please immediately notify the sender by replying to this email message, or by telephone, and delete the message from your email system. -- > -----Original Message----- > From: security400-bounces@xxxxxxxxxxxx > [mailto:security400-bounces@xxxxxxxxxxxx] On Behalf Of Dan > Sent: Friday, November 11, 2005 11:46 AM > To: Security Administration on the AS400 / iSeries > Subject: Re: [Security400] Program object's USRPRF(*USER > vs. *OWNER) effectonauthorities required to run certain > things. > > On 11/11/05, John Earl <john.earl@xxxxxxxxxxxxx> wrote: > > > > > QUESTION: Do they really mean to imply the _user > profile_ > > > in effect at the > > > time the command is being executed, and not the > signed-on > > > _user_? > > > > They mean the user profile _in_effect_. That means if > you are using > > program profile adoption, then it is the combined > authorities of the > > Signed on User and the Owner(s) of the adopting > program(s) being > > executed. > > > > If you are using swapped profile, it is simply the > authority of the > > "Current" user. > > > In our particular case, either way we are covered. > > But I'm curious about the "swapped profile" comment. Are > you referring to > the QSYGETPH and QWTSETP duo? Or something else? > > - Dan > _______________________________________________ > This is the Security Administration on the AS400 / iSeries > (Security400) mailing list > To post a message email: Security400@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/mailman/listinfo/security400 > or email: Security400-request@xxxxxxxxxxxx > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/security400. >
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.