Alan,
the rsu level of the zvm 5.3 is 0701. This systems runs on a t-server.
But I think that this cannot be an issue because everything is virtually
built by zvm so the hardware shouldn't be an issue or could it make
sense to test the same scenario on a real z-machine. Is it possible
that zos needs an additional option in user direct. Currently there are
the same options than on a vse 2.7 which works fine with the virtual
qdio. What I know definitely is that this zos has formerly worked with a
real osa qdio in an lpar on a 9672. So I would say there shouldn't be
missing ptfs on the zos side.
kind regards
Franz Josef Pohlen
Alan Altmark schrieb:
On Sunday, 08/12/2007 at 10:13 EDT, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
Hi listers,
I have a problem in setting up the guest lan for a zOS 1.5 on my zVM
5.3. With a VSE 2.7 guest it works perfect but not with the zOS.
The messages while starting the tcpip device are the following:
15.00.37 MVS1 v tcpip,,start,glanqdio
15.00.38 MVS1 STC03011 EZZ0060I PROCESSING COMMAND: VARY TCPIP,,START,
GLANQDIO
15.00.38 MVS1 STC03011 EZZ0053I COMMAND VARY START COMPLETED
SUCCESSFULLY
15.00.38 MVS1 STC03011 EZZ4308I ERROR: CODE=8010002A DURING ACTIVATION
OF DEVICE GLANQDIO. DIAGNOSTIC CODE: 02
15.00.38 MVS1 STC03010 IST1631I TRL0E00 SUBCHANNEL 0E01 QDIO DEVICE
TYPE
NOT OSD
I have defined the devices in HCD as CHPID 01 OSD and devices as OSA. I
have attached a text file with the complete config (HCD, TCPPROF,
VTAM-TRL Guestlan/NIC-defs). In the mail body it is sometimes a bit
difficult to read the lines because of the line breaks. I think I have a
mistake somewhere or I miss something. I've checked already the
archives, but the related items didn't lead me to the solution. What I
don't understand is, that it complains about E01 not to be a QDIO
device. I think that zVM should simulate that to the guest and on zOS I
have defined it as OSA Express as you can see in the file.
I didn't see anything wrong, but make sure you are current with CP and
z/OS Comms Server service. I would be tempted to call the Support Center
(Comms Server) and explain the problem. As you say, the virtual NICs are
QDIO.
Alan Altmark
z/VM Development
IBM Endicott
