RE: Problems with adopting authority

Kurt:

Yeah, I guess my wording was a little vague at a number of points -- better I'd 
said at step 3 also to grab the current user profile handle for use later. (But 
Rob's shown that he's pretty good, so I tend to skip things with him.)

My understanding is that profiles such as QTCP are restricted in this way 
primarily in order to prevent switching _to_ those profiles. The provision of 
*CURRENT for the UserId parm avoids this issue in the case where the programmer 
is switching _from_ those profiles and needs to return later..

You (or anyone else) wouldn't happen to have additional thoughts on other 
reasons these profiles might be restricted?

Tom Liotta

midrange-l-request@xxxxxxxxxxxx wrote:

>   4. RE: Problems with adopting authority (Kurt Goolsbee)
>
>QTCP is protected from being used by the swap APIs - You can't get a profile
>handle for it.
>
>    5. Then immediately switch back to whatever user was running the job
>(possibly QTCP).
>
>> -----Original Message-----
>> From: qsrvbas@xxxxxxxxxxxx [SMTP:qsrvbas@xxxxxxxxxxxx]
>> Sent: Friday, March 21, 2003 5:25 PM
>> To:   midrange-l@xxxxxxxxxxxx
>> Subject:  RE: Problems with adopting authority
>>
>> Rob:
>>
>> I'd try it this way...
>>
>> 1. Leave owner as QSECOFR (or better, a *SECOFR but not QSECOFR).
>> 2. Leave program as usrprf( *OWNER ).
>> 3. Early in the program, switch to an authorized profile that can execute
>> user profile changes.
>> 4. Call QCAPCMD (or whatever) to do the work.
>> 5. Then immediately switch back to whatever user was running the job
>> (possibly QTCP).

-- 
-- 
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788 x313
Fax    253-872-7904
http://www.powertechgroup.com


__________________________________________________________________
Try AOL and get 1045 hours FREE for 45 days!
http://free.aol.com/tryaolfree/index.adp?375380

Get AOL Instant Messenger 5.1 for FREE! Download Now!
http://aim.aol.com/aimnew/Aim/register.adp?promos=380455