Re: SUSE12 Gold image on VM
On Wednesday, 06/17/2015 at 07:03 EDT, Martin Schwidefsky martin.schwidef...@de.ibm.com wrote: Well, technically there have been machines with OSA cards that required the portname which is why the parameter has survived until now. There is a bit in the response block of the read channel activation ccw that tells us if the portname is required. The 9672s were the last machines that required a portname, but perhaps just following the rules dictated by that bit is sufficient. With the option for 31-bit kernel builds gone from the upstream source and the fact that the z900/z800 does not require the portname we could remove the portname code from the OSA driver. Uschi, care to create a patch to remove everything portname related from the OSA driver? Ummm. I wouldn't do that. I simply want the documentation to disappear and any distro-provided configuration panels to remove it. If someone already has it, accept it, warn that it is being ignored, and ignore it. I don't want failures because someone specifies the portname. And it is still an attribute of the OSA, even if Linux isn't using it. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SUSE12 Gold image on VM
On 6/18/2015 at 10:56 AM, Alan Altmark alan_altm...@us.ibm.com wrote: Ummm. I wouldn't do that. I simply want the documentation to disappear and any distro-provided configuration panels to remove it. If someone already has it, accept it, warn that it is being ignored, and Whereas I would prefer to have the entire concept vanish. If something can only cause problems/confusion, there's no up side to keeping it. ignore it. I don't want failures because someone specifies the portname. And it is still an attribute of the OSA, even if Linux isn't using it. There wouldn't be any failures if someone provides a portname in a parmfile, for instance. The installer would ignore it as would the kernel. As for being an attribute of the OSA I'm sure there are _plenty_ of other attributes that exist that people outside of IBM don't even know about. If we can safely ignore those, then we can safely ignore this one. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SUSE12 Gold image on VM
On Thursday, 06/18/2015 at 11:45 EDT, Mark Post mp...@suse.com wrote: There wouldn't be any failures if someone provides a portname in a parmfile, for instance. The installer would ignore it as would the kernel. As for being an attribute of the OSA I'm sure there are _plenty_ of other attributes that exist that people outside of IBM don't even know about. If we can safely ignore those, then we can safely ignore this one. The important thing is the parm files. If it's being ignored there, then I guess it's ok to let it quietly slip unlamented into oblivion. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SUSE12 Gold image on VM
I agree with Mark .. from everything I've read in these threads and documentation - the 'safest' course is to not specify the portname - and there is no downside to not specifying it but can be to having it specified -- so have the driver ignore any configuration that attempts to specify it. Then remove it from distro doc and config panels. As long as you 'can' use the driver to update it... I don't see the why the distros should 'hide' it or try to explain you should really leave this parm alone when the driver fully supports updating it. This one's on IBM to deal with first, imho. Let's make our driver eliminate future failure/confusion. I'm sure there are arguments for providing 'full functionality' - but I prefer we keep the foot wound safety on until someone can provide a meaningful use for this field someday if ever. Scott Rohling On Thu, Jun 18, 2015 at 8:44 AM, Mark Post mp...@suse.com wrote: On 6/18/2015 at 10:56 AM, Alan Altmark alan_altm...@us.ibm.com wrote: Ummm. I wouldn't do that. I simply want the documentation to disappear and any distro-provided configuration panels to remove it. If someone already has it, accept it, warn that it is being ignored, and Whereas I would prefer to have the entire concept vanish. If something can only cause problems/confusion, there's no up side to keeping it. ignore it. I don't want failures because someone specifies the portname. And it is still an attribute of the OSA, even if Linux isn't using it. There wouldn't be any failures if someone provides a portname in a parmfile, for instance. The installer would ignore it as would the kernel. As for being an attribute of the OSA I'm sure there are _plenty_ of other attributes that exist that people outside of IBM don't even know about. If we can safely ignore those, then we can safely ignore this one. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Fw: SUSE12 Gold image on VM
Martin, yes, I can take care about removing the portname from the qeth driver. Regards, Uschi Martin Schwidefsky/Germany/IBM wrote on 17/06/2015 09:24:59: From: Martin Schwidefsky/Germany/IBM To: Mark Post mp...@suse.com, Ursula Braun1/Germany/IBM@IBMDE, Cc: Linux on 390 Port LINUX-390@VM.MARIST.EDU Date: 17/06/2015 09:25 Subject: Re: SUSE12 Gold image on VM Mark Post mp...@suse.com wrote on 06/16/2015 04:53:29 PM: From: Mark Post mp...@suse.com To: Linux on 390 Port LINUX-390@VM.MARIST.EDU, Date: 06/16/2015 04:53 PM Subject: Re: SUSE12 Gold image on VM On 6/16/2015 at 09:55 AM, Alan Altmark alan_altm...@us.ibm.com wrote: On Tuesday, 06/16/2015 at 12:50 EDT, Mark Post mp...@suse.com wrote: On 6/15/2015 at 11:54 PM, Alan Altmark alan_altm...@us.ibm.com wrote: Neither z/VM nor Linux have to specify a portname (real or virtual). I recommend that you do NOT specify the portname. I don't understand why the distros still worry about the portname. We got rid of the requirement for z/VM and Linux on the z900 and z800 back in 2003. Just issue a msg that it's obsolete and ignore it. Even for Linux in an LPAR sharing an OSA with a z/OS system that is specifying (their equivalent of) a portname? Yes, even then. You can google OSA portname relief. OK then. I'm going to open up a bug with IBM to either remove that attribute from the driver, or make it read-only in sysfs. Preferably removing it altogether since it can only cause problems by being present. Looking at the results of my Google searches, I can see why I never made the complete connection. There were always statements made about z/OS requiring the parameter, and if you specify it in Linux it has to match. Looking at it now, I understand what was meant. Back then it meant (to me and apparently others) if you're sharing an OSA you need to specify the same portname as z/OS is using. Well, technically there have been machines with OSA cards that required the portname which is why the parameter has survived until now. There is a bit in the response block of the read channel activation ccw that tells us if the portname is required. With the option for 31-bit kernel builds gone from the upstream source and the fact that the z900/z800 does not require the portname we could remove the portname code from the OSA driver. Uschi, care to create a patch to remove everything portname related from the OSA driver? blue skies, Martin Martin Schwidefsky Linux on System z Development IBM System Technology Group, System Software Development IBM Deutschland Research Development GmbH Vorsitzender des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SUSE12 Gold image on VM
Mark Post mp...@suse.com wrote on 06/16/2015 04:53:29 PM: From: Mark Post mp...@suse.com To: Linux on 390 Port LINUX-390@VM.MARIST.EDU, Date: 06/16/2015 04:53 PM Subject: Re: SUSE12 Gold image on VM On 6/16/2015 at 09:55 AM, Alan Altmark alan_altm...@us.ibm.com wrote: On Tuesday, 06/16/2015 at 12:50 EDT, Mark Post mp...@suse.com wrote: On 6/15/2015 at 11:54 PM, Alan Altmark alan_altm...@us.ibm.com wrote: Neither z/VM nor Linux have to specify a portname (real or virtual). I recommend that you do NOT specify the portname. I don't understand why the distros still worry about the portname. We got rid of the requirement for z/VM and Linux on the z900 and z800 back in 2003. Just issue a msg that it's obsolete and ignore it. Even for Linux in an LPAR sharing an OSA with a z/OS system that is specifying (their equivalent of) a portname? Yes, even then. You can google OSA portname relief. OK then. I'm going to open up a bug with IBM to either remove that attribute from the driver, or make it read-only in sysfs. Preferably removing it altogether since it can only cause problems by being present. Looking at the results of my Google searches, I can see why I never made the complete connection. There were always statements made about z/OS requiring the parameter, and if you specify it in Linux it has to match. Looking at it now, I understand what was meant. Back then it meant (to me and apparently others) if you're sharing an OSA you need to specify the same portname as z/OS is using. Well, technically there have been machines with OSA cards that required the portname which is why the parameter has survived until now. There is a bit in the response block of the read channel activation ccw that tells us if the portname is required. With the option for 31-bit kernel builds gone from the upstream source and the fact that the z900/z800 does not require the portname we could remove the portname code from the OSA driver. Uschi, care to create a patch to remove everything portname related from the OSA driver? blue skies, Martin Martin Schwidefsky Linux on System z Development IBM System Technology Group, System Software Development IBM Deutschland Research Development GmbH Vorsitzender des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SUSE12 Gold image on VM
On Tuesday, 06/16/2015 at 12:50 EDT, Mark Post mp...@suse.com wrote: On 6/15/2015 at 11:54 PM, Alan Altmark alan_altm...@us.ibm.com wrote: Neither z/VM nor Linux have to specify a portname (real or virtual). I recommend that you do NOT specify the portname. I don't understand why the distros still worry about the portname. We got rid of the requirement for z/VM and Linux on the z900 and z800 back in 2003. Just issue a msg that it's obsolete and ignore it. Even for Linux in an LPAR sharing an OSA with a z/OS system that is specifying (their equivalent of) a portname? Yes, even then. You can google OSA portname relief. I've posted this a few times, from October 2003: An OSA-Express microcode update for the IBM zSeries z800 and z900 machines became available today that makes the portname optional for the OSA-Express in QDIO mode. The update is Driver 3G - EC stream J11204, MCL032 (OSA level 3.33). This is a functional change that has already been made for the z990 and is now backfitted to earlier hardware levels. z/VM has released two APARs in support of these changes at the z/VM 4.3.0 level (these were already included in the z/VM 4.4.0 base): VM63308 - PORTNAME relief for z/VM Guest LAN PQ73878 - VM TCP/IP exploitation of PORTNAME relief If you are using real OSA-Express devices in QDIO mode and have the hardware update applied, the PORTNAME is no longer required when configuring OSD devices. For compatibility, OSA-Express will permit activation with or without a PORTNAME. For the z/VM Guest LAN environment with VM63308 applied, the portname specification is also optional. Prior to this change, if you were sharing an OSA-Express, you needed to configure matching names for all shared devices. If a mismatch occurred, activation would fail. Now you can omit the portname. The June 2003 Linux distribution also contains support for portname relief. The portname is still required for z/OS. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SUSE12 Gold image on VM
On 6/16/2015 at 09:55 AM, Alan Altmark alan_altm...@us.ibm.com wrote: On Tuesday, 06/16/2015 at 12:50 EDT, Mark Post mp...@suse.com wrote: On 6/15/2015 at 11:54 PM, Alan Altmark alan_altm...@us.ibm.com wrote: Neither z/VM nor Linux have to specify a portname (real or virtual). I recommend that you do NOT specify the portname. I don't understand why the distros still worry about the portname. We got rid of the requirement for z/VM and Linux on the z900 and z800 back in 2003. Just issue a msg that it's obsolete and ignore it. Even for Linux in an LPAR sharing an OSA with a z/OS system that is specifying (their equivalent of) a portname? Yes, even then. You can google OSA portname relief. OK then. I'm going to open up a bug with IBM to either remove that attribute from the driver, or make it read-only in sysfs. Preferably removing it altogether since it can only cause problems by being present. Looking at the results of my Google searches, I can see why I never made the complete connection. There were always statements made about z/OS requiring the parameter, and if you specify it in Linux it has to match. Looking at it now, I understand what was meant. Back then it meant (to me and apparently others) if you're sharing an OSA you need to specify the same portname as z/OS is using. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SUSE12 Gold image on VM
Or make the driver ignore anything specified and set it to null/blank ... ? Scott Rohling On Tue, Jun 16, 2015 at 7:53 AM, Mark Post mp...@suse.com wrote: On 6/16/2015 at 09:55 AM, Alan Altmark alan_altm...@us.ibm.com wrote: On Tuesday, 06/16/2015 at 12:50 EDT, Mark Post mp...@suse.com wrote: On 6/15/2015 at 11:54 PM, Alan Altmark alan_altm...@us.ibm.com wrote: Neither z/VM nor Linux have to specify a portname (real or virtual). I recommend that you do NOT specify the portname. I don't understand why the distros still worry about the portname. We got rid of the requirement for z/VM and Linux on the z900 and z800 back in 2003. Just issue a msg that it's obsolete and ignore it. Even for Linux in an LPAR sharing an OSA with a z/OS system that is specifying (their equivalent of) a portname? Yes, even then. You can google OSA portname relief. OK then. I'm going to open up a bug with IBM to either remove that attribute from the driver, or make it read-only in sysfs. Preferably removing it altogether since it can only cause problems by being present. Looking at the results of my Google searches, I can see why I never made the complete connection. There were always statements made about z/OS requiring the parameter, and if you specify it in Linux it has to match. Looking at it now, I understand what was meant. Back then it meant (to me and apparently others) if you're sharing an OSA you need to specify the same portname as z/OS is using. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SUSE12 Gold image on VM
On Tuesday, 06/16/2015 at 11:41 EDT, Duerbusch, Tom duerbus...@stlouis-mo.gov wrote: Back in the old days, SLES 7, the statement about portname was, it is not required, but if you do use it, you must use it every where (or something to that effect). So, as I never when back to the older running images to delete the portname, I still continue to specify the portname on all new images. So, the question is, can I have a mixture of images that specify a portname with images that do not specify a portname? Also, I have running images that goes back to SLES9 running. Does your answer go all the way back to SLES9? (I'm on a z/890almost everything I run is currently unsupported G) I can't speak to SLES requirements, but as far as the OSAs go, the portname is optional. IF it is specified, then it must match anyone else who also specified the portname, be they z/OS, Linux, VM, or VSE. So, yes, you can mix specify/unspecified on the port. All the 'specified' hosts must use the same value. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SUSE12 Gold image on VM
Thanks Alan I'll drop portname from my install documentation and, eventually, when we get a new processor, we can go to SLES 12 and beyond, and portnames will eventually die out (no zOS here...for bettor or worse). Tom Duerbusch THD Consulting On Tue, Jun 16, 2015 at 11:00 AM, Alan Altmark alan_altm...@us.ibm.com wrote: On Tuesday, 06/16/2015 at 11:41 EDT, Duerbusch, Tom duerbus...@stlouis-mo.gov wrote: Back in the old days, SLES 7, the statement about portname was, it is not required, but if you do use it, you must use it every where (or something to that effect). So, as I never when back to the older running images to delete the portname, I still continue to specify the portname on all new images. So, the question is, can I have a mixture of images that specify a portname with images that do not specify a portname? Also, I have running images that goes back to SLES9 running. Does your answer go all the way back to SLES9? (I'm on a z/890almost everything I run is currently unsupported G) I can't speak to SLES requirements, but as far as the OSAs go, the portname is optional. IF it is specified, then it must match anyone else who also specified the portname, be they z/OS, Linux, VM, or VSE. So, yes, you can mix specify/unspecified on the port. All the 'specified' hosts must use the same value. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SUSE12 Gold image on VM
On 6/15/2015 at 11:54 PM, Alan Altmark alan_altm...@us.ibm.com wrote: Neither z/VM nor Linux have to specify a portname (real or virtual). I recommend that you do NOT specify the portname. I don't understand why the distros still worry about the portname. We got rid of the requirement for z/VM and Linux on the z900 and z800 back in 2003. Just issue a msg that it's obsolete and ignore it. Even for Linux in an LPAR sharing an OSA with a z/OS system that is specifying (their equivalent of) a portname? Can you point me to where that is documented? Being partially responsible for linuxrc, and I get rid of the check for it if it is truly obsolete in all cases on all hardware. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SUSE12 Gold image on VM
Jake, Do you have some specific questions you are looking to have answered? This may be too generic a request. Specific areas of interest? Lizette -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Jake Anderson Sent: Monday, June 08, 2015 10:50 AM To: LINUX-390@VM.MARIST.EDU Subject: SUSE12 Gold image on VM Hi Does anyone have experiences in building SUSE12 using VNC? I would like to have some discussion on the same. If anyone is willing to help and explain that would be really of a great help. Jake -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
SUSE12 Gold image on VM
Hi Does anyone have experiences in building SUSE12 using VNC? I would like to have some discussion on the same. If anyone is willing to help and explain that would be really of a great help. Jake -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SUSE12 Gold image on VM
On 6/8/2015 at 01:50 PM, Jake Anderson justmainfra...@gmail.com wrote: Hi Does anyone have experiences in building SUSE12 using VNC? I do. :) I would like to have some discussion on the same. If anyone is willing to help and explain that would be really of a great help. What would you like to know? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
