You need to plan how many subplexes are needed, assign
group IDs, ensure that all TCP/IP stacks and VTAM® nodes in the sysplex are at z/OS® V1R8 or later, and assign VLAN IDs as needed.
Before you begin
Steps 2 and 3 depend on the level of isolation you require
for your subplexes within the sysplex. Those two steps are not needed
when the following conditions are true:
- You do not use HiperSockets™ in
support of dynamic XCF connectivity
- You do not need to isolate the subplexes for HiperSockets connectivity (if, for example,
you need only to restrict sysplex distributor distribution between
subplexes)
- You can configure your systems such that TCP/IP stacks that are
in separate subplexes and are on the same CPC use a CHPID that is
unique to the subplex
Requirement: A z890 GA2 or z990
GA2 hardware level is required to support VLAN IDs on HiperSockets.
Procedure
Perform the following steps to prepare your sysplex for
subplexing.
- Plan how many subplexes are needed and assign a TCP/IP
XCF group ID and a VTAM XCF
group ID for each anticipated subplex in the sysplex:
- All TCP/IP stacks in the same TCP/IP subplex must have the same
TCP/IP XCF group ID.
- All VTAM nodes in the same VTAM subplex must have the same VTAM XCF group ID.
- Ensure that all TCP/IP stacks and VTAM nodes in the sysplex are at z/OS V1R8 or later.
- If HiperSockets is
enabled and there are TCP/IP stacks in the sysplex that are on the
same CPC and use the same HiperSockets CHPID,
assign a VLAN ID to each anticipated subplex in the sysplex. Also,
assign a VLAN ID to the default subplex (that is, the subset of sysplex
TCP/IP stacks that uses the default sysplex group name, EZBTCPCS).
All TCP/IP stacks in the same subplex must have the same VLAN ID,
if they are on the same CPC and use the same HiperSockets CHPID.