Malcolm
There's something a bit fishy here!
Making the DEVICE name the same as the TRLE name does *not* correspond to
what I just posted on the IBMTCP-L list concerning the relationship between
the TRLE statement and the DEVICE statement.
Thus I was obliged actually to go to the manuals where I find the following:
From the CS IP Configuration Reference:
<quote>
DEVice device_name MPCIPA NONRouter PRIRouter SECRouter NOAUTORestart
AUTORestart
...
device_name The name of the device. The device name must be the PORT name of
the LAN adapter defined in a TRLE for a QDIO connection. The maximum length
is eight characters.
</quote>
I'll admit that's a bit ambiguous. What's a PORT name when it's at home?
From The CS SNA Resource Definition Reference:
<quote>
PORTNAME=(port_name,link_num)
Dependency:
OSA port operating in either ATM native mode or in QDIO mode. Specify
link_num only for an OSA-Express port operating in QDIO mode customized for
LAN emulation.
port_name
Specifies the OSA port name. The name must be unique within one logical
partition and it must be unique for an OSA port shared by multiple logical
partitions. The maximum length for port_name is 8 characters.
For an IBM Open Systems Adapter (OSA) port customized for HPDT ATM native
mode, port_name must match the portname specified at OSA customization
through OSA/SF. If used by TCP/IP, this name must also be defined as the
portname in the TCP/IP Profile DEVICE statement. If used for SNA HPR over
native ATM connection, this name must also be defined as the portname in the
PORT statement in a VTAM XCA major node.
For an IBM Open Systems Adapter-Express (OSA-Express) port operating in QDIO
mode, the name specified for the port_name value is downloaded into the OSA
at the time the first TCP/IP device for this OSA port is activated. For
OSA-Express QDIO connections, this name must also be defined as the device
name in the TCP/IP profile DEVICE statement for any TCP/IP stack that will
use this OSA-Express feature. This name must also be defined as the port
name on a VARY TCPIP,,OSAENTA command or the port name on an OSAENTA profile
statement when a TCP/IP stack will start an OSA-Express network traffic
analyzer trace on this OSA.
</quote>
"For OSA-Express QDIO connections, this name must also be defined as the
device name in the TCP/IP profile DEVICE statement for any TCP/IP stack that
will use this OSA-Express feature." corresponds to the post I made in the
IBMTCP-L list, namely that the DEVICE statement name must be the same as the
name specified by the PORT operand of the TRLE statement.
There is also the following:
<quote>
name
...
On TRLE: Assigns a required name for the TRLE. This name cannot match the
VTAMLST member name containing this Transport resource list major node.
For an IBM Open Systems Adapter (OSA) port customized for HPDT ATM native
mode, the name must match the OSA name specified at OSA customization
through OSA/SF. If used by TCP/IP, the OSA name must also be specified as
the device name in the TCP/IP profile DEVICE statement.
For an IBM Open Systems Adapter-Express (OSA-Express) port operating in QDIO
mode the name specified here will be downloaded into the OSA-Express as OSA
name at the time the TCP/IP device for this OSA connection is activated.
</quote>
Are you using an Open Systems Adapter (OSA) port customized for HPDT ATM
native mode?
Chris Mason
----- Original Message -----
From: "Malcolm Beattie" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Tuesday, October 02, 2007 12:12 PM
Subject: Re: z/OS using a guest virtual LAN under z/VM
Raymond Noal writes:
Does anybody have a z/OS system (I'm using 1.8, but it does not have to
be) running in a virtual machine under z/VM (I'm using 5.3.0, but it
does not have to be) and the z/OS virtual machine is connected to a
guest virtual LAN.
Yes, (z/OS 1.6 under z/VM 5.1.0 at the moment). You configure
virtual OSA NICs the same as real ones.
If so, can you please answer the following questions:
1) what is the OSA CHPID type defined as for your z/VM system?
2) what are the DEVICE and LINK statements defining your guest
virtual LAN for your TCPIP virtual machine?
3) what are the DEVICE and LINK statements for z/OS's TCP/IP
definitions for the connection to the guest virtual LAN?
Doing a lot of RTFM-ing, it seems that the CHPID type must be OSA
Express in QDIO mode (TYPE=OSD in the I/O Config.) and the virtual LAN
segment must also be in QDIO mode (the only other choice is HIPERSOCKETS
- DEFINE LAN VMLAN1 QDIO OWNER SYSTEM in the SYSTEM CONFIG file).
Yes, that'll do fine.
The
DEVICE and LINK statements for TCP/IP in z/OS seem to be:
DEVICE ZVMLAN1 MPCIPA NONROUTER
LINK VLAN1 IPAQENET ZVMLAN1
Yes.
But there is mention made of requiring a TRL and TRLE definition running
in VTAM. Is this TRUE? I find it difficult to believe that I have to
involve VTAM in this configuration. But, then again, .....
You do need such a definition to map the "ZVMLAN1" word above to the
underlying device number triple. For my configuration, I have
DEVICE TRLF7004 MPCIPA NONROUTER
LINK LNKLOCAL IPAQENET TRLF7004
for a virtual NIC interface onto a GuestLAN and the corresponding VTAM
definition (continuation characters omitted):
TRLV7004 VBUILD TYPE=TRL
*
*
TRLF7004 TRLE LNCTL=MPC,
READ=7004,
WRITE=7005,
DATAPATH=7006,
PORTNAME=OSA7004,
MPCLEVEL=QDIO
--
Malcolm Beattie <[EMAIL PROTECTED]>
Linux Technical Consultant, IBM Europe System z
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
