Check for duplicate class names
Description
When new classes are shipped with RACF®, you should verify that any installation-defined class names that have been added to the class descriptor table (CDT) do not conflict with the new classes. For a list of new classes shipped with RACF, see z/OS Summary of Message and Interface Changes.
Table 1 provides more details about this migration action. Use this information to plan your changes to the system.
| Element or feature: | Security Server. |
|---|---|
| When change was introduced: | General migration action not tied to a specific release. |
| Applies to migration from: | z/OS V2R1 and z/OS V1R13. |
| Timing: | Before the first IPL of z/OS V2R2. |
| Is the migration action required? | Yes, if you have user-defined classes. |
| Target system hardware requirements: | None. |
| Target system software requirements: | None. |
| Other system (coexistence or fallback) requirements: | None. |
| Restrictions: | None. |
| System impacts: | None. |
| Related IBM® Health Checker for z/OS® check: | None. |
Steps to take
Verify that any installation-defined class names that have been added to the class descriptor table (CDT) do not conflict with the new classes.
- If you have duplicate class names, RACF issues the following message
and enters failsoft mode:
ICH564A RACF DETECTED AN ERROR IN THE INSTALLATION CLASS DESCRIPTOR TABLE, ENTRY class_name, ERROR CODE 7 - If a conflict in class names occurs, resolve it as follows:
- Delete the profiles in the installation-defined class with the conflicting name.
- Delete the CDT entry for the class.
- Add a CDT entry with a different name.
- Redefine the profiles.
Reference information
For more information, see z/OS Security Server RACF System Programmer's Guide.