Odd behavior with profile handle switching

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

-- 
David Gibbs
david@xxxxxxxxxxxx