IRRH502I

Explanation
The RACF UNIX identity check
has determined that you want RACF® to
assign unique UNIX IDs when
users or groups without OMVS segments use certain z/OS® UNIX services.
Assigning unique UNIX identities
rather than shared identities improves overall security and increases
user accountability.
RACF automatically
assigns unique UNIX identities
for z/OS UNIX services when all of the following requirements
are satisfied:The RACF database is enabled
for application identity mapping (AIM) stage 3.
The UNIXPRIV class profile SHARED.IDS is defined and the UNIXPRIV
class is active and RACLISTed.
The FACILITY class profile BPX.NEXT.USER is defined and its APPLDATA
field has valid ID values or ranges.
The FACILITY class profile BPX.UNIQUE.USER is defined.

See  z/OS Security Server RACF Security Administrator's Guide for
more information about enabling RACF for
automatic assignment of unique UNIX identities.
The
check produces a report listing the requirements for this support.
 An "E" in the "S" (Status) column indicates that a requirement is
not satisfied.  For example, if the RACF database
has not been enabled for AIM stage 3, this requirement is flagged
as an exception.  If the "S" field is blank, the requirement is satisfied.
 If there are no exceptions indicated in the Status column, all requirements
are satisfied.Note:  The check validates that the FACILITY class profile
BPX.NEXT.USER APPLDATA field is present, not that it has valid ID
values or ranges.

System action
The check continues processing.  There is no effect
on the system.

Operator response
None.

System programmer response
None.

Problem determination

Source

Module
IRRHCR10

Routing code
N/A

Descriptor code
N/A

Automation
None.

Reference Documentation
See  z/OS Security Server RACF Security Administrator's Guide.