The in-storage profile pname was too large to be RACLISTed.

If the profile is defined to RACF in more than one way, for example, as a member of a grouping class profile and as a profile in the corresponding member class, RACF merges the multiple definitions to form a resulting in-storage profile. It may be the combination of the two or more definitions of the profile, not the individual definitions themselves, that caused the profile to be too large.

If pname is identified as a group member in the message, you can issue the RLIST classname pname RESGROUP command to locate all the grouping class profiles that have it as a member.

Decrease the size of the profile (or its associated profiles). The standard and conditional access lists are the most likely areas to cause the profile to grow. Other areas to consider are the installation data, the application data, or categories.

After you have made the profile smaller, reissue the SETROPTS RACLIST command or have the application reissue the RACROUTE REQUEST=LIST request. If the profile is generic, issue the SETROPTS GENERIC(classname) REFRESH command.

For more information about the size restriction of an in-storage profile, see topic in the z/OS Security Server RACF Security Administrator's Guide on "Limiting the Size of Your Access Lists".