© Copyright IBM Corporation, 2008
OSA-Express3 Definitions
1.0 Introduction
With the introduction of OSA-Express3 and the dual density of ports per CHPID, there
has been confusion as to how these should be defined in IOCP (or via HCD/HCM) and
how one would specify the ports to be used. The following will illustrate how these new
OSA-Express3 cards will be defined.
Note: Since there are multiple ports per CHPID, both of the ports associated with the
CHPID will be the same, i.e. OSD, OSE, OSC,etc. It is not possible, for example, to
have one port defined as OSC and the other as OSD. It is possible, however, to have
different CHPID types for the same card where the card does support multiple
CHPIDs.
The following tables illustrate the options available and the resulting number of ports that
can be used for the z10:
TABLE 1. OSA-Express3 1000 Base-T Options
OSA-Express3
Feature
1000Base-T 2-Port
1 CHPID
1000Base-T 4-Port
2 CHPIDS
OSA-Express3 Definitions
CHPID
Type
Available Ports
Notes
OSC
Two of two ports available
2 ports per CHPID
z10 BC Only
OSD
Two of two ports available
2 ports per CHPID
z10 BC Only
OSE
Two of two ports available
2 ports per CHPID
z10 BC Only
OSN
LPAR to LPAR only
z10 BC Only
OSC
Four of four ports available
2 ports per CHPID
z10 EC and z10 BC
OSD
Four of four ports available
2 ports per CHPID
z10 EC and z10 BC
OSE
Four of four ports available
2 ports per CHPID
z10 EC and z10 BC
OSN
LPAR to LPAR only
z10 EC and z10 BC
December 11, 2009
1
© Copyright IBM Corporation, 2008
TABLE 2. OSA-Express3 10 GbE
OSA-Express3
Feature
CHPID
Type
10 GbE LR 2-Port
Available Ports
Notes
OSD
Two of two ports available
1 port per CHPID
z10 BC and z10 EC
OSD
Two of two ports available
1 port per CHPID
z10 BC and z10 EC
Available Ports
Notes
2 CHPIDs
10 GbE SR 2-Port
2 CHPIDs
TABLE 3. OSA-Express3 GbE
OSA-Express3
Feature
CHPID
Type
GbE 2 Port SX
OSD
Two of two ports available
2 ports per CHPID
z10 BC Only
OSN
LPAR to LPAR Only
z10 BC Only
OSD
Four of four ports available
2 ports per CHPID
z10 BC and z10 EC
OSN
LPAR to LPAR only
z10 BC and z10 EC
OSD
Four of four ports available
2 ports per CHPID
z10 BC and z10 EC
OSN
LPAR to LPAR only
z10 BC and z10 EC
1 CHPID
GbE 4 Port SX
2 CHPIDs
GbE 4 Port LX
2 CHPIDs
2.0 Definitions for CHPID type OSD
Below can be seen the IOCP definitions for an OSD CHPID. Note that in the IOCP there
is no reference to a port. That is handled via the TRLE statements shown later.
CHPID PATH=(CSS(0,1),02),SHARED, PARTITION=((CSS(1),(A12),(=))),
PCHID=1C0,TYPE=OSD
CNTLUNIT CUNUMBR=2980,PATH=((CSS(0),02),(CSS(1),02)),UNIT=OSA
IODEVICE ADDRESS=(2980,015),UNITADD=00,CUNUMBR=(2980),UNIT=OSA
IODEVICE ADDRESS=298F,UNITADD=FE,CUNUMBR=(2980),UNIT=OSAD
Below are the corresponding VTAM TRLE definition examples which may be of interest
when the mode selected is for QDIO (CHPID type=OSD) and which show how the port
for this multiple ports/CHPID can be identified.
For this example, this is for the devices on CHPID 02.
OSA2980 VBUILD TYPE=TRL
OSA2980P TRLE LNCTL=MPC,
READ=2980,
WRITE=2981,
OSA-Express3 Definitions
December 11, 2009
2
© Copyright IBM Corporation, 2008
DATAPATH=2982,
(Note 1)
PORTNAME=OSA2980, (Note 2)
MPCLEVEL=QDIO
OSA2986 VBUILD TYPE=TRL
OSA2986P TRLE LNCTL=MPC,
READ=2986,
WRITE=2987,
DATAPATH=2988,
PORTNAME=OSA2986,
PORTNUM=1,
MPCLEVEL=QDIO
Note 1: Each port uses three device numbers (1. READ/ 2. WRITE/ 3. DATAPATH). There are two
exceptions:
• If more than one TCPIP stack in "one" LPAR, one additional DATAPATH device is needed.
• If the OSA Network Analyzer Trace is being used (available at z/OS V1R9), one additional
DATAPATH device is needed.
Note 2: PORTNUM=0 is not coded, but it could be. PORTNUM=0 is default if not coded
Also included is the VTAM display for OSA2986P so that you can see the PORTNUM
field:
SC81D NET,TRL,TRLE=OSA2986P
IST097I DISPLAY ACCEPTED
IST075I NAME = OSA2986P, TYPE = TRLE
IST1954I TRL MAJOR NODE = OSA2986
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST087I TYPE = LEASED
, CONTROL = MPC , HPDT = YES
IST1715I MPCLEVEL = QDIO
MPCUSAGE = SHARE
IST2263I PORTNAME = OSA2986
PORTNUM = 1 OSA CODE LEVEL = 0704
IST1577I HEADER SIZE = 4096 DATA SIZE = 0 STORAGE = ***NA***
IST1221I WRITE DEV = 2987 STATUS = ACTIVE
STATE = ONLINE
IST1577I HEADER SIZE = 4092 DATA SIZE = 0 STORAGE = ***NA***
IST1221I READ DEV = 2986 STATUS = ACTIVE
STATE = ONLINE
IST1221I DATA DEV = 2988 STATUS = ACTIVE
STATE = N/A
IST1724I I/O TRACE = OFF TRACE LENGTH = *NA*
IST1717I ULPID = TCPIP
IST1815I IQDIO ROUTING DISABLED
IST1918I READ STORAGE = 4.0M(64 SBALS)
IST1757I PRIORITY1: UNCONGESTED PRIORITY2: UNCONGESTED
IST1757I PRIORITY3: UNCONGESTED PRIORITY4: UNCONGESTED
IST2190I DEVICEID PARAMETER FOR OSAENTA TRACE COMMAND = 00-01-00-08
IST1801I UNITS OF WORK FOR NCB AT ADDRESS X'11150010'
IST1802I P1 CURRENT = 0 AVERAGE = 0 MAXIMUM = 0
IST1802I P2 CURRENT = 0 AVERAGE = 0 MAXIMUM = 0
IST1802I P3 CURRENT = 0 AVERAGE = 0 MAXIMUM = 0
IST1802I P4 CURRENT = 0 AVERAGE = 1 MAXIMUM = 2
IST1221I DATA DEV = 2989 STATUS = RESET
STATE = N/A
IST1724I I/O TRACE = OFF TRACE LENGTH = *NA*
IST1221I DATA DEV = 298A STATUS = RESET
STATE = N/A
IST1724I I/O TRACE = OFF TRACE LENGTH = *NA*
OSA-Express3 Definitions
December 11, 2009
3
© Copyright IBM Corporation, 2008
IST1221I DATA DEV = 298B STATUS = RESET
STATE = N/A
IST1724I I/O TRACE = OFF TRACE LENGTH = *NA*
IST314I END
Below is a pictorial representation of the above definitions and how they relate to the ports
on the card:
FIGURE 1. VTAM Definitions
3.0 Definitions for CHPID type OSE
The above is strictly for the QDIO mode when the CHPID is defined as OSD. For the nonQDIO definitions, the CHPID type would be defined as OSE. As with the OSD definition,
there are no IOCP parameters for identifying the port for that CHPID. The discussion
below will show how that is determined.
OSA-Express3 Definitions
December 11, 2009
4
© Copyright IBM Corporation, 2008
A lot of customers who have not upgraded all of their SNA network to Enterprise
Extender are running native SNA and you cannot run native SNA and QDIO mode concurrently. Other customers are also running TCP/IP pass thru mode for their IP network.
For the SNA side of the house, an XCA Major node for LAN and ATM LAN emulation
connections is coded. In the SNA Resource Definition Reference Manual, see LAN and
ATM LAN emulation connections. This is the way OSA-Express in native SNA mode
has always been defined, but there was never a requirement to code the ADAPNO parameter. This is because there was always only 1 port per CUA, and the ADAPNO parameter
defaulted to 0. However, with the new dual density 1000BASE-T OSA-Express3's, it is
required to define the ADAPNO parameter (in the manual, it says "Specifies a relative
adapter number assigned to each adapter or port by an IBM 3172 Nways Interconnect
Controller or an Open Systems Adapter."), The value used would be the same number as
the PORTNUM parameter if this were being defined for QDIO mode. Therefor, define the
OSA-Express for native SNA just like prior versions of the OSA-Express but now code
the ADAPNO parameter to indicate which port is being used (0-1).
For TCP/IP implementations, it is the same as an OSA-Express device defined for TCP/IP
pass thru mode. One would define a DEVICE and LINK statement for an LCS device. In
the IP Configuration Reference manual, see DEVICE and LINK -- LAN Channel Station
and OSA devices statement. In this case, it was never a requirement to define a link number on the link statement since the link number defines what OSA calls the "port number".
Prior to OSA-Express3, there was always only 1 port per CUA and thus the link number
defaulted to 0. With OSA-Express3, the link number should be set to the appropriate port
number (in the manual, it is stated as follows - "If defining OSA, this value is the port
number on the OSA"). Therefore, define the OSA-Express for TCP/IP pass thru mode just
like before but now define a link number to indicate which port you are using (0-1).
4.0 Definitions for CHPID type OSC
Initially, when the CHPID type was defined as OSC, then the second port for the CHPID
was disabled and not usable and there would only be one port per CHPID that could be
used. With the release of driver code in November 2009, this restriction was lifted and all
ports can now be used on OSA-Express3 for all configuration setups, including when the
CHPID is defined as OSC. The IOCP definitions are the same as the previous families of
OSA-Express.
When an OSC CHPID is defined in the IOCP, then there will be two ports on the card that
will be used for OSC. The place to resolve which port is to be used will be in the customization panels on the HMC for the card.
OSA-Express3 Definitions
December 11, 2009
5
© Copyright IBM Corporation, 2008
FIGURE 2. OSC Port Definitions (HMC)
5.0 Software Requirements
There are minimum software requirements associated with the implementation of OSAExpress3 technology and the PSP Buckets and related manuals should be reviewed for
those requirements.
OSA-Express3 Definitions
December 11, 2009
6