We have a program that an operator uses when setting up a new user. It basically does a RTVUSRPRF on an existing user and then issues a CRTUSRPRF on the new user with values from the existing user. This has been used for years, but I'm running into an issue this morning.
The program uses adopted authority.
Program is receiving an error on the CRTUSRPRF stating not authorized to a Group Profile. The Group Profile is a supplemental group.
While trying to diagnose the problem, I had the operator run this program on a different user that uses a different Group Profile. This time the program worked.
I have checked the authority on both of the group profiles. Both are owned by QSECOFR with *public Exclude and with *GROUP QSECOFR.
I cannot find any difference in these 2 Group Profiles other than the list of users with authority. In both cases the Profile being copied also has authority to the Group Profile.
The operator running the program does not have specific authority to either of these Group Profiles.
The CRTUSRPRF is being executed via a QCMDEXC in an RPGLE program.
It appears Adoption is working up to the point of the CRTUSRPRF specifically for this 1 Group Profile.
I feeling like I'm missing something simple, but I'm not sure what.
NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.
This mailing list archive is Copyright 1997-2019 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