A slight correction... It's VMRMSVM that manages the share settings not PerformanceToolkit.. There are many ways to influence how VMRMSVM manages the share values. The concept is similar to setting PRTY in VSE, the partitions with the highest I/O (high wait states) gets the higher priority and the partitions with the lower IO rates (less wait state) gets a lower priority.
On Mon, Feb 7, 2011 at 11:13 AM, McBride, Catherine <cmcbr...@kable.com>wrote: > A while ago a very experienced VM person from IBM suggested that we not > use ABSOLUTE unless you "absolutely" must cap off a guest to keep it > from running away with your real processors. We used that setting on > our test system only. > Our VSE TOR and VM guest TCPIP both had high relative shares (10000 > versus 3000 for regular production guests). > Then we started using a performance manager feature of VM Toolkit, it > managed share values for us. > It set everything the same after VM IPL, but by the end of a normal > production day our busiest guests had dropped to the lowest relative > share, the ones seldom used had the highest. Meaning my understanding > of how relative share worked was backwards or the gizmo in VM Toolkit > was. Hopefully Alan or Kris will expound. > > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On > Behalf Of Hughes, Jim > Sent: Monday, February 07, 2011 12:57 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: SET SHARE ABSOLUTE/RELATIVE > > I've read the CP COMMAND manual and the PERFORMANCE manual regarding the > SET SHARE command and how it works. > > Would someone care to comment on how you have used them for your z/VSE > production and guest machines? > > What would suggest for TCPIP/RSCS/VTAM SET SHARE values? > > Thanks in advance. > > > ____________________ > Jim Hughes > Consulting Systems Programmer > Mainframe Technical Support Group > Department of Information Technology > State of New Hampshire > 27 Hazen Drive > Concord, NH 03301 > 603-271-5586 Fax 603.271.1516 > > Statement of Confidentiality: The contents of this message are > confidential. Any unauthorized disclosure, reproduction, use or > dissemination (either whole or in part) is prohibited. If you are not > the intended recipient of this message, please notify the sender > immediately and delete the message from your system. >
