|
"John Earl" <john.earl@xxxxxxxxxxxxxxxxxx> wrote in message news:003201c32633$473a3350$bf01000a@xxxxxxx > Some other questions... > Who has authority to *USE User QSECOFR Nobody involved. Program X adopts QSECOFR authority. > Who owns, and who has authority to *USE User A > Who owns, and who has authority to *USE User B Don't know ... not sure what difference that makes. Program X should be operating with QSECOFR authority. > 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? It's when switching from A to B. > 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? No, handle for user B was retrieved immediately prior to invoking QWTSETP. This issue was encountered on a customers system ... and we tested the function on our system without a problem. I suspect it's the fact that the profile was in the QSECOFR group. david
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.