RE: Problems with adopting authority

[qsrvbas@xxxxxxxxxxxx (Tom Liotta)]

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).

This way, usrprf(*OWNER) has authority to switch both ways and the switched-to 
profile has authority to do the work without requiring adopted authority.

You should only need to create the one switched-to profile unless you also 
choose to create the alternative *SECOFR profile (a very good idea, avoiding 
QSECOFR).

Tom Liotta

midrange-l-request@xxxxxxxxxxxx wrote:

>   9. Re: Problems with adopting authority.
>
>IBM responded to my pmr.  Working as designed.  You cannot access a user 
>profile with adopted authority.  Via QCAPCMD, CL program or anything.
>
>Suggestion:  Grant QTCP access to that user profile.
>
>Scares me at first, but the more I study that it sounds reasonable.  But 
>I'd appreciate comments from y'all.

-- 
-- 
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