Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Enabling IPv6 support z/OS Communications Server: IPv6 Network and Application Design Guide SC27-3663-00 |
|
z/OS®Communications Server
can be run as an IPv4-only stack or as a dual-mode stack (IPv4 and
IPv6). The BPXPRMxx parmlib member determines which mode is used.
The following configurations are possible:
Restriction: After a stack has been started, you must
stop and restart the stack to change the mode of the stack.
You can configure AF_INET alone or both AF_INET and AF_INET6. Although coding AF_INET6 alone is not prohibited, TCP/IP does not start because the master socket is AF_INET and the call to open it fails. INET IPv4-only BPXPRMxx sample definitionIPv4-only stack support is defined by using one NETWORK statement (for AF_INET) in the BPXPRMxx parmlib member. For example:
INET IPv4/IPv6 dual-mode stack BPXPRMxx sample definitionDual-mode
stack support is defined by using two NETWORK statements (one for
AF_INET and one for AF_INET6) in the BPXPRMxx parmlib member. For
example:
Separate MAXSOCKETS values are supported. The IPv6 default is the IPv4 specified value. CINET IPv4-only BPXPRMxx sample definitionMultiple
TCP/IP stacks in one MVS™ image
or LPAR are supported only by using Common INET (CINET). Each TCP/IP
stack is defined in the BPXPRMxx parmlib member using a SUBFILESYSTYPE
statement. These definitions are identical to what was used before
IPv6 support. The following example shows the definitions for three
IPv4-only stacks:
CINET IPv4/IPv6 dual-mode stack BPXPRMxx sample definitionDual-mode (IPv4/IPv6) stack support is defined by using two NETWORK statements in the BPXPRMxx member. Each TCP/IP stack is defined in the BPXPRMxx parmlib member by using a SUBFILESYSTYPE statement. All z/OS Communications Server stacks that are defined under the two NETWORK statements are dual-mode (IPv4/IPv6) stacks. The following example shows the definitions for three dual-mode stacks:
|
Copyright IBM Corporation 1990, 2014
|