ICH408I

Explanation
An attempt was made to dub a process and the OMVS
segment in the current user's USER profile has no z/OS UNIX user identifier
(UID) assigned or the profile for either the user's current connect
group or the user's default group does not have an z/OS® UNIX group
identifier (GID) assigned.  Both the current connect group and default
group must have GIDs.

System action
RACF® returns
an error return code to the invoking system function, which returns
an error return code to the application caller or causes the calling
task to abend.  See z/OS UNIX System Services Programming: Assembler Callable Services Reference to
determine the action of the syscall functions.

Programmer response
Provide appropriate information about the
failure to the user of your program, based on the function invoked
and the return codes received. If you were expecting a UID or GID
to be automatically assigned during processing of the BPX.UNIQUE.USER
profile in the FACILITY class, the service might fail for one of the
following reasons:The BPX.UNIQUE.USER profile is not defined.
The UNIXPRIV class SHARED.IDS profile is not defined.
The RACF database is not
converted to stage 3 of application identity mapping.
The BPX.NEXT.USER profile in the FACILITY class is not defined.
The BPX.NEXT.USER profile in the FACILITY class does not define
a valid UID or GID range.
The range defined in the BPX.NEXT.USER profile in the FACILITY
class has no remaining UID or GID values.

See z/OS Security Server RACF Security Administrator's Guide for
more information about automatically assigning UIDs and GIDs. There
might also be symptom records in the LOGREC data set that can be used
to help diagnose the error.  See z/OS Security Server RACF System Programmer's Guide for
more information about possible symptom records.