TDP3624 "npname" ENVIRONMENT COULD NOT BE INITIALIZED
Explanation:
When STARTing an NP, the operating system rejected TDP's attempt to use the system's Internet Protocol instance specified by the TDP CONFIG NP IPSTACK command.
Generated By:
TDP.
Notes:
The NP enters the PERM ERR state and will not be used. There is no impact to any Database NP.
Remedy:
The MVS userid assigned to any TDP using an NP must be defined to the MVS RACF OMVS segment in the user profile to provide a UNIX userid. For IBM's RACF, this may be done in one of three ways. For z/OS V1.R13 and older, the BPX.DEFAULT.USER RACF FACILITY class can be used to assign a default Unix userid to every MVS userid. For z/OS V1.R11 and later, the BPX.UNIQUE.USER RACF FACILITY class can be used to request a Unix userid for any MVS userid without an OMVS segment that accesses a UNIX kernel service. For any z/OS release, the following RACF commands may be used to associate an existing UNIX userid to an MVS TDP userid: "ALTUSER mvsusername OMVS(UID(unixuserid)" and "ALTGROUP mvsgroupname OMVS(GID(unixgroupid))", where mvsusername is the MVS userid for the TDP, unixuserid is either an existing UNIX user id or the parameter AUTOUID to request that a unique UNIX userid be generated; mvsgroupname is the MVS group name with which the MVS TDP user name is associated; unixgroupid is either an existing UNIX user id or the parameter AUTOGID to request that a unique UNIX userid be generated.