ICH14074I

Explanation
EGN (enhanced generic naming) was in effect and
NOEGN was specified on the SETROPTS command. Some generic profiles
containing an * or ** that were created while EGN was in effect, do
not protect any resources when NOEGN is in effect. For example, profile
'USER1.AB.**.CD' protects USER1's data sets AB.CD and AB.EF.CD when
EGN is in effect.  'USER2.GH.*' protects USER2's data sets GH.IJ and
GH.KL. The profiles, created when EGN was in effect, are not recognized
when NOEGN is in effect and do not protect any resources.

System action
The command proceeds and NOEGN is placed in effect.

User response
Do one of the following tasks: If the change to NOEGN caused some resources to become unprotected,
issue SETROPTS EGN to place EGN in effect .
If placing NOEGN in effect does not leave resources unprotected,
then no action is required.

 Contact your system administrator if you need help determining
whether any resources must be protected.

RACF® Security
Administrator Response
Be sure that no resources are left
unprotected when NOEGN is placed in effect. Use the SEARCH and LISTDSD
commands to determine what profiles are defined and which profile
protects a particular resource. See "Naming Considerations For Resource
Profiles" in z/OS Security Server RACF Command Language Reference for
a discussion of the differences between generic profile protection
with EGN and NOEGN.

Explanation

System action

User response

RACF® Security Administrator Response