Specifying BPXPRMxx values for a CINET configuration

For a detailed description of parameters in SYS1.PARMLIB(BPXPRMxx), see z/OS UNIX System Services Planning and z/OS MVS Initialization and Tuning Guide.

Figure 1. SYS1.PARMLIB(BPXPRMxx) for CINET

 
/* AF_INET file system for sockets      */
/* CINET support - BPXTCINT  */
 
FILESYSTYPE TYPE(CINET)
            ENTRYPOINT(BPXTCINT) ¹
NETWORK DOMAINNAME(AF_INET)
        DOMAINNUMBER(2)
        MAXSOCKETS(10000) ²        TYPE(CINET)
        INADDRANYPORT(40000) ³
        INADDRANYCOUNT(2000)
NETWORK DOMAINNAME(AF_INET6)⁴
        DOMAINNUMBER(19)
        MAXSOCKETS(10000) ²        TYPE(CINET)
SUBFILESYSTYPE NAME(TCPIP1A) ⁵
               TYPE(CINET)
               ENTRYPOINT(EZBPFINI) ⁶
               DEFAULT ⁷
SUBFILESYSTYPE NAME(TCPIP1B) ⁵
               TYPE(CINET)
               ENTRYPOINT(EZBPFINI)

Notes:

CINET and BPXTCINT specify the use of CINET.
The MAXSOCKETS operand specifies the maximum number of sockets that can be obtained for the given file system type. It should be large enough for the number of sockets needed for applications using z/OS® Communications Server. MAXSOCKETS is enforced independently for AF_INET (IPv4 sockets) and AF_INET6 (IPv6 sockets).
The INADDRANYPORT and INADDRANYCOUNT operands specify the first ephemeral port number and the range of ports to be used by z/OS UNIX CINET. The port range specified should also be reserved for CINET use in the TCP/IP profile using the port reservation statements. For details, see Port reservation across multiple transport providers. You can use IBM® Health Checker for z/OS to check whether the range of ports specified is reserved for OMVS on the TCP/IP stack. For more information about IBM Health Checker for z/OS, see z/OS Communications Server: IP Diagnosis Guide.
This additional NETWORK statement is required if you want a TCP/IP stack to also support IPv6. Omit this statement if you do not want the stack to support IPv6 (that is, the stack will support IPv4 only).
A transport provider stack for CINET is specified with a SUBFILESYSTYPE statement. The NAME field must match the address space name for the TCP/IP started task as well as the TCPIPJOBNAME parameter in TCPIP.DATA. In our example, the name of the first stack is TCPIP1A and the name of the second stack is TCPIP1B.
EZBPFINI identifies a z/OS Communications Server TCP/IP stack. For a z/OS Communications Server TCP/IP stack, this is the only valid value.
Keyword DEFAULT specifies which transport provider stack is to be used as the default stack for z/OS UNIX. If DEFAULT is not specified, the first active stack will be used as the default stack. The sequence of SUBFILESYSTYPE statements is arbitrary if one stack is identified with the keyword DEFAULT. TCPIP1A is the default stack in Figure 1.