Another quick question... do you know if zOS 1.4 supports both types of guest lans (type=qdio and type=hipers).
I could not get the type=qdio to work either....so that's why i am trying
type=hipers now.
Dave Myers
Denver Solutions Group
Senior Systems Engineer
Office Phone:�� (303) 996-7112
Cellular Phone: (303) 619-0782
Home Office:��� (303) 948-0027
Fax:����������������� (303) 706.1713
e-mail: [EMAIL PROTECTED]
Dennis
Musselwhite To: [EMAIL PROTECTED]
<[EMAIL PROTECTED] cc:
m.com> Subject: Re: Need help figuring out why
my zOS1.4 VNIC won't come active on GUESTLAN
Sent by: Linux TYPE=HIPERS
on 390 Port
<[EMAIL PROTECTED]
ARIST.EDU>
02/06/2003
02:37 PM
Please respond
to Linux on 390
Port
Hi,
You mentioned that you picked CHPID number 03 to use...
> TCPIP PROFILE:
> -----------------------------
> DEVICE IUTIQD03 MPCIPA
> LINK HIPERL03 IPAQIDIO IUTIQD03
>
> Note: the "03" designates the CHPID to use for IQD...and
> since 03 was not in use...I picked this one.
Normally, CP manages the CHPID assignment for your guest virtual
machine to avoid conflicts with hardware CHPID assignments. We
had to adjust for the explicit use of CHPID numbers in z/OS
configuration by creating a CHPID option on the CP DEFINE NIC
command. Did you add CHPID 03 to your DEFINE NIC command?
This (by the way) is the ONLY time the CHPID option should be used
for a simulated NIC... when you have to give z/OS a predictable CHPID.
You can use the CP DISPLAY SCHIB command to get that information.
If (for example) you define NIC 500 CHPID 03 and device 500 is
assigned to subchannel 016, you can issue CP DISPLAY SCHIB 016
and the column under CHPID0-3 should have 03000000.
If the CHPID was assigned properly in your virtual machine,
perhaps you need to DEFINE the NIC and COUPLE it before you
IPL the z/OS guest? I don't know whether z/OS gathers all of the
necessary channel characteristics when a device is added dynamically.
You are correct in that you do NOT need to HCD gen the HiperSockets device
(Guest LAN is fully simulated within the CP layer of z/VM).
Regards,
Dennis Musselwhite ([EMAIL PROTECTED])
IBM z/VM Development -- CP Network Simulation
