Right, generate more. Change that ,03 to a higher number. I have 16, but I suspect you can go much higher.
Marcy Cortes Wells Fargo Services Company -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Booher Sent: Thursday, April 08, 2004 14:03 To: [EMAIL PROTECTED] Subject: Re: [LINUX-390] VSWITCH question So, my current IOCP has: CNTLUNIT CUNUMBR=0100,PATH=(00),UNIT=OSA IODEVICE ADDRESS=(0100,03),CUNUMBR=(0100),UNIT=OSA, X UNITADD=00 IODEVICE ADDRESS=(010F),CUNUMBR=(0100),UNIT=OSAD, X UNITADD=FE Should I generate more OSA IODEVICE addresses, say 0103, 0104, and 0105 and use 0103 as the RDEV for the VSWITCH? What's confusing is that VSWITCH RDEV wants a REAL device, so is it possible to generate more addresses for the real OSA? Dave -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Ferguson, Neale Sent: Thursday, April 08, 2004 3:50 PM To: [EMAIL PROTECTED] Subject: Re: VSWITCH question The VSWITCH OSA devices are attached to no one. CP will drive them but use the VM TCPIP stack to initialize the devices. CP uses the *VSWITCH IUCV service to talk with the stack. The stack will issue the necessary CCWs to get the OSAs initialized. From that point on CP will drive the devices itself and the stack is "out of the loop". So the answer is: use OSA devices not currently in use. Alan Altmark gave an extremely interesting and detailed presentation on just this issue at today's Hillgang meeting. Neale ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
