z/OS Security Server RACF Security Administrator's Guide
z/OS Security Server RACF Security Administrator's Guide
Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Specifying an ambiguous custom field keyword z/OS Security Server RACF Security Administrator's Guide SA23-2289-00 |
|
On releases before z/OS® V2R1, if
you attempt to add data specifying an ambiguous custom field keyword,
messages are issued. For example, if your installation has defined
two custom field names that are ambiguous subsets of each other, such
as the names HOME and HOMEADDR, when you attempt to add data for the
HOME field, you receive messages similar to the following messages:
Examples:
Starting with z/OS V2R1, you can add data for a custom field whose name is a subset of another custom field’s name, so long as you fully specify the custom field name on commands. For example, if your installation has defined two custom fields named HOME and HOMEADDR, you can add data to the custom field HOME, so long as you fully specify HOME. If you attempt to add data specifying a shortened custom field name that is ambiguous, messages are issued. For example, if your installation has defined two custom fields HOME and HOMEADDR, when you attempt to add data using a shortened custom field name, such as HOM, you receive a message similar to: IRR52119I Keyword name abbreviation HOM is ambiguous. 
|
 Copyright IBM Corporation 1990, 2014 |
