Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Data set naming convention table z/OS Security Server RACF System Programmer's Guide SA23-2287-00 |
|
The data set name format used by RACF® is based on the TSO data set naming rules (see z/OS TSO/E User's Guide). In addition to these rules, RACF requires the data set name to have at least two qualifiers and the high-level qualifier to be a valid RACF-defined user ID or group name. RACF allows installations to create a naming convention table (ICHNCV00) that RACF uses to check the data set name in all the commands and RACROUTE requests that process data set names. This table helps an installation set up and enforce data set naming conventions that are different from the standard RACF naming conventions. You create the naming convention table by using the ICHNCONV macro. (For information on coding the ICHNCONV macro, see z/OS Security Server RACF Macros and Interfaces.) If the required processing is too complex to be handled by using
the ICHNCONV macro, you can use exit routines to modify data set naming
conventions. A naming convention routine or table should
be able to perform the following functions:
RACF processes the naming
convention table before
it calls the following exit routines:
The RACF initialization routine finds the ICHNCV00 module and stores the address in the RCVT. If the initialization routine finds the module, ICHNCV00 is listed in message ICH508I with the other exit routines. If you change ICHNCV00, you must reassemble it, link-edit it, and re-IPL. ICHNCV00 has AMODE(31) and RMODE(ANY). You cannot override these values. See also Command exits for specific commands. |
Copyright IBM Corporation 1990, 2014
|