Am I the first? That is what we were taught with 390 systems. You also didn't want your communications region to be paged out (set reserved for those). You always gave communications very high priority. You didn't want your 3270 traffic waiting. If, due to resources, you needed to wait, you waited in CICS or DB2, both of which used variable amount of resources for any transaction. But 3270 traffic, same old, same old, day to day. Get it processed as fast as you can.
Obviously, FTP thru a monkey wrench if the stack that serviced FTP was high priority. Direct printing wasn't a problem with a high priority stack, but now that all printing is buffered, you don't want printing to be on a high priority stack either. The paper and your point seems to only be for Linux systems. And they are unique things compared to historic 390 processing. It would be interesting to see the same experiment done with multiple VSE systems. Anyway, I think the point is that Linux isn't a traditional 390 Operation System. And you can't take they things you know and apply them to Linux with a near 100% success rate. Using my, home grown performance tool, over the span of months, I see my 16 VSE systems taking resources just like we were taught (200 is twice as much as 100). But my IFL side, not that we are normally busy enough for relative shares to take effect, just didn't seem to match up with the relative shares defined. The paper did explain things. OK, so it didn't make sense, but that is why a lot of us thing "relative shares" the way we do. Tom Duerbusch THD Consulting >>> Rob van der Heij <[email protected]> 6/14/2011 3:56 PM >>> On Tue, Jun 14, 2011 at 7:57 PM, Scott Rohling <[email protected]> wrote: As for "wrong" - I thought that was beaten to death already. I buy an adult beverage for the first* who can explain why it makes sense to have the TCPIP stacks with a relative share 30 times higher than their Linux production guests. Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/ ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
