IRRB023I

Explanation
RACF® invoked
a UNIX service to dub the RACF subsystem address space as
a UNIX process, but the service
failed with the return and reason codes specified.   RACF only invokes UNIX services
during subsystem initialization if a RACF function
that requires UNIX (for example,
password enveloping) is enabled.  The most likely cause of this failure
is that the subsystem address space identity does not have an OMVS
segment.  If so, you might see an ICH408I message in addition to IRRB023I.Note: If
the RACF subsystem address
space has the PRIVILEGED attribute, the ICH408I message is not displayed
because audit records are not created for PRIVILEGED tasks

System action
The RACF subsystem
continues to initialize.  Functions that require z/OS® UNIX System
Services are not available.

Routing code
2

Descriptor code
6

RACF Security
Administrator Response
If the subsystem address space identity
is not defined as a UNIX user,
define an OMVS segment for its USER profile and for its default group
profile.  See z/OS Security Server RACF Security Administrator's Guide for
details on defining UNIX users.
The RACF subsystem user ID
does not require, and should not be assigned, a UID value of 0.  Unless
message IRRC040I was also issued, the RACF subsystem
address space must be stopped and restarted after the OMVS information
is defined for the UNIX functions
to become available. To avoid interruptions in services that are provided
by the address space, it should be restarted during a period of low
activity.  See z/OS Security Server RACF System Programmer's Guide for
information about the RACF subsystem.
If
the RACF subsystem address
space identity is defined as a UNIX user,
consult z/OS UNIX System Services Programming: Assembler Callable Services Reference for
the meaning of the return and reason codes

Explanation

System action

Routing code

Descriptor code

RACF Security Administrator Response