RE: Odd behavior with profile handle switching

["John Earl" <john.earl@xxxxxxxxxxxxxxxxxx>]

I doubt it has anything to do with the differences between user Class
and Group.  

Something in the back of my mind tells me that you are having problems
with Special Authorities.  IIRC - Special authorities cannot be adopted
from a group profile.  This means that even though user B is a member of
the group QSECOFR, it does not help you during these adopted program
calls.

Some other questions...
Who has authority to *USE User QSECOFR
Who owns, and who has authority to *USE User A
Who owns, and who has authority to *USE User B
Do you know if the authority error comes from user A swapping to user B,
or does it come from User B trying to swap back to user A?

The other possibility at work here is that the QWTSETP API requires a
user to have both *USE authority to the User profile you are switching
to, as well as to all of that profiles groups.  This is not documented
in the API reference, but that don't mean it is not so.  Your test of
removing B from QSECOFR's group seems to bear this out.

Finally, the API reference lists CPF2217 as a valid error for the
QWTSETP (or QsySetToProfileHandle), but does not indicate when or how
such a message could be generated.  Is it possible that the profile
handle is not the correct one for the swap you are trying?  Did you
store and use the wrong handle?

Hopefully there is something for you to run with in all of that.

jte


> I ran into some odd behavior with user profile handle
> switching the other
> day.
> 
> Program X is owned by QSECOFR and adopts authority.  This
> program switches
> it's user profile handle to "B" midstream, does stuff, and
> switches back to
> the original handle.
> 
> User profile A is class *PGMR.
> User profile B is class *PGMR and in the QSECOFR group.
> 
> If user profile A runs program X I get a CPF2217 error,
> Not authorized to
> user profile QSECOFR, when we are trying to switch to
> profile B.
> 
> When we remove profile B from the QSECOFR group, it
> appears to work fine.
> 
> My thinking is that somehow the fact that the users class
> and group are
> contradictory might be causing some problem.
> 
> Any thoughts?
> 
> Thanks!
> 
> david
>