Common z/OS UNIX configuration problems

The following list includes some explanations and possible solutions for common problems that you might encounter when you are configuring the z/OS® UNIX environment.

TCP/IP initialization fails with the following messages:
```
EZZ4203I Z/OS UNIX-TCP/IP CONNECTION ERROR FOR TCPIP-BPX1SOC,
     00000003,FFFFFFFF,00000070,112B00B6
```
These messages usually indicate that both INET and CINET FILESYSTYPE have been specified. Only one should be specified; see the FILESYSTYPE information in z/OS UNIX System Services Planning for additional information.
TCP/IP initialization fails with the following messages:
```
EZZ4203I Z/OS UNIX-TCP/IP CONNECTION ERROR FOR TCPIP-BPX1SOC,
     00000003,FFFFFFFF,0000006F,112B00B0 
```
These messages indicate that the requester of the service is not privileged. The service requested requires a privileged user. Check the documentation for the service to understand what privilege is required.
TCP/IP initialization fails with the following messages:
```
EZZ4203I Z/OS UNIX-TCP/IP CONNECTION ERROR
     FOR TCPIPA-BPX1IOC,8008C981,FFFFFFFF,0000009E,12B2005A
 
EZZ4204I TCPIP INITIALIZATION FOR TCPIPA FAILED
```
These messages usually indicate that an incorrect jobname was specified in the SUBFILESYSTYPE NAME() definition in the BPXPRMxx member for a common INET environment. In this scenario, the NAME() must match TCPIPA.
TCP/IP initialization fails with the following messages:
```
IEA8481 DUMP SUPPRESSED - ABDUMP MAY NOT DUMP STORAG FOR KEY 0-7 JOB TCPV34A
IEF4501 TCPIPA TCPIPA - ABEND=SEC6 U0000 REASON=0F01C008
```
These messages are usually an indicator that an OMVS RACF® segment has not been defined for the user ID associated with the TCP/IP started procedure. Define an OMVS segment with a UID of 0 for the user ID associated with the TCP/IP started procedure.

TCP/IP initialization fails with the following messages:

IEF4031 TCPIPA - STARTED - TIME=16.01.25
EZZ4203I Z/OS UNIX-TCP/IP CONNECTION ERROR FOR TCPIPA-BPX11OC,
     8008139A,FFFFFFFF,00000079,12D2025E
EZZ4204I TCPIP INITIALIZATION FOR TCPIPA FAILED.
 
==> The 0079 value is EINVAL - The parameter is incorrect
==> The 025E value is JRSocketCallParmError - A socket syscall
    contains incorrect parameters

These messages usually indicate that an incorrect entry point name has been specified in the SUBFILESYSTYPE ENTRYPOINT() definition. The correct value is ENTRYPOINT(EZBPFINI).

TCP/IP initialization fails with the following messages:
```
EZZ4203I Z/OS UNIX-TCP/IP CONNECTION ERROR FOR TCPIPA-BPX1SOC,
     00000003,FFFFFFFF,0000045A,112B0000
EZZ4204I TCPIP INITIALIZATION FOR TCPIPA FAILED.
 
==> The 045A value is EAFNOSUPPORT - The address family is not supported
```
These messages indicate that AF_INET was not defined or did not initialize properly. Check for any earlier z/OS UNIX messages and verify that the z/OS UNIX NETWORK DOMAINNAME(AF_INET) statement is in your BPXPRMxx member.

After issuing a NETSTAT command from TSO, the following message is displayed:

netstat
CEE5101C During initialization, the z/OS UNIX callable service
     BPX1MSS failed. The system return code was 0000000156,
     the reason code was 0507014D. The application will be
     terminated.
NETSTAT ENDED DUE TO ERROR+
READY
?
USER ABEND CODE 4093 REASON CODE 00000090
READY
 
==> The 0156 value is EMVSINITIAL - Process initialization error
==> The 014D value is JRFsFailChdir - The dub failed, due to
    an error with the initial home directory

These messages indicate that the user ID issuing the NETSTAT command does not have an OMVS RACF segment defined for it. Define an OMVS segment for this user ID or activate the automatic assignment of unique UNIX identities support. For details, see UNIX System Services security considerations.

Socket applications using the z/OS Communications Server TCP/IP Services APIs fail with an ERRNO of 156.
ERRNO 156 indicates a z/OS UNIX process initialization failure. This is usually an indication that an appropriate OMVS RACF segment is not defined for the user ID associated with the application. The RACF OMVS segment may not be defined or may contain errors such as an improper HOME() directory specification. If the OMVS segment is not defined, you may also receive the following message:
```
ICH4081 USER(USER8   ) GROUP(SYS1   )   NAME(TSO USERID USER8  )
   CL(PROCESS )
   OMVS SEGMENT NOT DEFINED
```
In this example, USER8 is the user ID associated with the failing application. To correct this problem, define an appropriate OMVS segment for the user ID associated with the failing application. For details, see UNIX System Services security considerations.