Chapter 6. Customization Considerations
This chapter identifies customization considerations for RACF.
For additional information,OS/390see Security Server (RACF) System
Programmer's Guide.
Customer Additions to the CDT
Installations must verify that classes | they have added to the class |
(CDT) do not conflict with new classes | shipped with RACF. If duplicate |
entries are detected, the following | error messages are issued at |
ŸFor a duplicate router table entry, RACF issues this message and processing:ICH527I RACF DETECTED AN ERROR IN THE INSTALLATION ROUTER
TABLE, ENTRY class_name, ERROR CODE 1.
ŸFor a duplicate CDT entry, RACF issues this message and enters fa
ICH511I RACF DETECTED AN ERROR IN THE INSTALLATION CLASS DESCRIPTOR TABLE, ENTRY class_name, ERROR CODE 7.
If a conflict in class names occurs, you must delete the profiles
Do not assemble the
Exit Processing
Effects of OS/390 OpenEdition DCE | Support on | ICHRCX01, ICHRCX02, |
and IRRSXT00 |
|
|
OS/390 OpenEdition | DCE support | can affect: |
Ÿ The RACROUTE REQUEST=AUTH preprocessing and processing exits
ŸThe IRRSXT00 installation exit
RACROUTE REQUEST=AUTH Preprocessing | and | ||
Postprocessing | Exits |
| |
RACF | support | for OS/390 OpenEdition DCE introduces new indicators in the | |
ACEE. | These | indicators mark | the ACEE clientas a ACEE. Client ACEEs are |
created by OS/390 OpenEdition and RACF on behalf of multithreaded unau application servers on OS/390. There are two types of client ACEE:
ŸUnauthenticated client ACEE
When | an unauthenticated client ACEE is used in an access control de |
two | authorization checks occur. |
Copyright IBM Corp. 1994, 1996 | 35 |