Question & Answer
Question
Why am I receiving message ICH408I with OMVS segment incompletely defined and DFHKE0501 with return code X'0000009C' and return reason of X'0B0C00FA' from the set_dub_default service-routine when starting my CICS region? This started occurring after upgrading to z/OS V2.1.
These are the messages I receive:
ICH408I USER(cicsuser) GROUP(cicsgrp) NAME(cicsint LINK ) CL(PROCESS ) OMVS SEGMENT INCOMPLETELY DEFINED
DFHKE0501 cicsproc THE KERNEL RECEIVED A RETURN VALUE OF X'FFFFFFFF', A RETURN CODE OF X'0000009C' AND A RETURN REASON OF X'0B0C00FA' FROM THE SET_DUB_DEFAULT SERVICE-ROUTINE.
The return reason X'0B0C00FA' meaning is "The current group does not have a GID defined in the OMVS segment."
Answer
You need to create an OMVS segment with a z/OS UNIX group identifier (GID).
As of z/OS V2.1, the ability to use default OMVS segments has been removed. All z/OS UNIX users or groups must now have OMVS segments defined for user and group profiles with unique user IDs (UIDs) and group IDs (GIDs). One solution is to use RACF support to automatically generate unique UIDs and GIDs on demand for users and groups that do not have OMVS segments defined. Support for automatic unique UID and GID generation has been available since z/OS V1.11 with the BPX.UNIQUE.USER profile. Support for the BPX.DEFAULT.USER profile was removed in z/OS V2.1.
The presentation Is It Your deFault? Removal of BPX.DEFAULT.USER Profile describes the history of using default profiles in USS, and detailed steps for migrating from BPX.DEFAULT.USER profile to the BPX.UNIQUE.USER profile,
CICS regions require access to directories and files in z/OS UNIX; what has changed is the requirement in z/OS V2.1 for uniqueness. See Giving CICS regions access to z/OS UNIX directories and files in the CICS TS documentation for more information.
Product Synonym
CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
26 February 2016
UID
dwa1254440