Specifications

Chapter 6. Multiple zPDT instances 77
VSWITCH for guest use. Using the IP address patterns from our other examples, we might
have the following addresses in Figure 6-1:
192.168.0.60 Linux IP address for the Ethernet adapter
192.168.0.60 port 3270 address for external TN3270e connections to aws3274
10.1.1.1 Linux IP address for the tunnel interface
192.168.0.61 z/VM IP address for Ethernet
10.1.1.2 z/VM IP address for the tunnel interface
192.168.0.62 z/OS #1 address for Ethernet
10.1.1.3 z/OS #1 address for the tunnel interface
192.168.0.63 z/OS #2 address for Ethernet
10.1.1.4 z/OS #2 address for the tunnel interface
127.0.0.1 localhost connection for local x3270 sessions
6.3 Independent instances
We can have two independent instances, meaning that emulated I/O devices are not shared
between the instances. In common terms, there is no shared DASD (or any other shared
device).
Figure 6-2 Independent instances
We assume an L03 license (and a base Linux machine with two or more processors) and we
have assigned two CPs (a CP and a zAAP) to one instance and one CP to the other instance.
Notice that different port numbers are needed in the 3270port statements in the devmaps.
Emulated device addresses (device numbers) are independent between the instances and
both might use the same addresses, as described here.
Each emulated OSA requires its own Ethernet adapter and two adapters are needed in this
case. Two emulated OSAs cannot share an Ethernet adapter. We arbitrarily assigned a tunnel
interface to one of the instances.
1
This example suggests LCS (non-QDIO) mode for both
instances, but they could both be QDIO or a mixture of LCS and QDIO.
2
Linux
Tunnel supports a single connection.
It could be either z/OS instance.
CHPID=F1 CHPID=F0
Ethernet adapter
Local x3270 sessions
aws3274
Local x3270 sessions
aws3274
awsosa awsosa awsosa
CP zAAP
z/OS-aprof1
TCP/IP
zPDT Instance
CP
z/OS-profSB
TCP/IP
zPDT Instance
Emulated
DASD
Tunnel Linux TCP/IP
Ethernet adapter