Chapter 4. Connectivity 125
Example 4-5 OSA-Express HOME addresses
HOME
10.10.2.232 OSA2080LNK
10.10.3.233 OSA20A0LNK
10.10.2.234 OSA20C0LNK
10.10.3.235 OSA20E0LNK
Define the characteristics of each LINK statement using BSDROUTINGPARMS
To define the link characteristics, such as MTU (1) and Subnet Mask (2), we used the
BSDROUTINGPARMS statement. If not supplied, defaults will be supplied from static routing
definitions in BEGINROUTES, OMPROUTE configuration (if OMPROUTE is running), or if
none supplied, the stack's interface layer based on hardware capabilities and characteristics
of devices and links. We defined our links with the highest MTU size, as shown in
Example 4-6.
Example 4-6 BSDRoutingparms statements
BSDROUTINGPARMS TRUE
; Link name MTU Cost metric Subnet Mask Dest address
STAVIPA1LNK 1492 1 0 255.255.255.252 0
OSA2080LNK 1492 0 255.255.255.0 2 0
OSA20A0LNK 1492 0 255.255.255.0 0
OSA20C0LNK 1492 0 255.255.255.0 0
OSA20E0LNK 1492 0 255.255.255.0 0
IUTIQDF4LNK 57344 0 255.255.255.0 0
IUTIQDF5LNK 57344 0 255.255.255.0 0
IUTIQDF6LNK 57344 0 255.255.255.0 0
; ENDBSDROUTINGPARMS
4.4.2 HiperSockets implementation
The steps to implement HiperSockets are basically the same as we did to implement the
OSA-Express devices. What changes is that there is no external configurations to be done,
and the TRLE is created dynamically by VTAM.
When defining an MPCIPA HiperSockets, use the DEVICE statement to specify the IQD
CHPID hexadecimal value. The reserved device name prefix IUTIQDxx must be specified.
The suffix xx indicates the hexadecimal value of the corresponding IQD CHPID that was
configured with HCD or IOCP. Figure 4-9 on page 118 shows the HiperSockets
implementation scenario.