Previous enhancements to TCP/IP have reduced the need for multiple TCP/IP stacks. CINET may still be a viable choice if you are isolating access from different networks to the same z/OS UNIX system. An example of such a situation would be internal company networks versus internet access.

Both this topic and z/OS Communications Server: IP Configuration Guide contain information about running one TCP/IP stack and multiple TCP/IP stacks

Local INET (LINET) has been retired. SUBFILESYSTYPE ENTRYPOINT(BPXTLINT) was originally supplied as an alternative stack under CINET for a performance enhancement for AF_INET socket sessions between programs on the same system. The performance improvements that have been made in the TCP/IP socket stack in the past have removed the need for LINET. If LINET is started, an informational message is sent to the system console and LINET will deactivate itself. This will not affect the use of sockets, and you can delete the definition of LINET from your BPXPRMxx member at your convenience.