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 -----Original Message----- I am confused about the RDEV setting on the DEFINE VSWITCH command. I currently have my OSA adapter (address 0100,0101,0102) attached to TCPIP and defined as: DEVICE [EMAIL PROTECTED] OSD 0100 PORTNAME QSPORT0 PRIR LINK VMTCPIP QDIOETHERNET [EMAIL PROTECTED] When I attempt to activate the VSWITCH, I get: set vswitch bigbang connect HCPSWU2838W Device 0100 specified for VSWITCH BIGBANG is already attached HCPSWU2832E The connection for VSWITCH SYSTEM BIGBANG is not active. HCPSWU2832E None of the RDEVs are available working QDIO OSA Express devices. Command complete Ready; T=0.01/0.01 15:44:09 Can the same device (0100) be used for both? Or must I use another OSA adapter that is NOT attached to TCPIP and in use. ---------------------------------------------------------------------- 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
