27.12.2012 Views

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

SET SHARE<br />

Responses<br />

Messages<br />

requirements can be compared. If the users are limited by the same<br />

bottlenecked resource, a RELATIVE SHARE user with twice the SHARE of<br />

another should run twice as fast.<br />

3. The target maximum share is applicable only to the <strong>CP</strong>U resource.<br />

If a target maximum share is specified, the user will not necessarily receive that<br />

amount of scheduled <strong>CP</strong>U resource. This is because a user will only receive<br />

more than the target minimum share for a resource when other users are not<br />

using all of their target minimum shares.<br />

4. When the limit option is specified alone (that is, without a share <strong>and</strong> without a<br />

maximum share being specified), only that option is changed. The userid retains<br />

its previous share <strong>and</strong> the maximum share is changed (if necessary) to match<br />

the new limit option. For example, if NOLIMIT is specified, then the pre-existing<br />

maximum share (if any), is reset to zero. Or, if LIMITHARD or LIMITSOFT is<br />

specified <strong>and</strong> there previously was no maximum share, then the maximum<br />

share is set equal to the user’s minimum share (with the specified ’hard’ or ’soft’<br />

characteristic).<br />

5. Due to the dynamics of <strong>VM</strong> systems <strong>and</strong> scheduling, the maximum share target<br />

is not always met. The actual usage should be within five percent of the system.<br />

The accuracy may be affected by the following:<br />

v running guest as a virtual MP<br />

v guest use of diagnose X'44'<br />

v running <strong>VM</strong> second level or on LPAR<br />

v low system utilization.<br />

6. When setting SHARE RELATIVE on a userid that has multiple <strong>CP</strong>Us, the<br />

minimum share that the system will assign is one per virtual <strong>CP</strong>U. For example,<br />

if you SET SHARE MAINT RELATIVE 1 <strong>and</strong> MAINT has five virtual <strong>CP</strong>Us, the<br />

resulting SHARE will be set to five.<br />

Response 1:<br />

USER userid: ABSOLUTE SHARE = nnn% [; m DEDICATED <strong>CP</strong>U[S]]<br />

MAXIMUM SHARE = option type value<br />

- or -<br />

H<strong>CP</strong>07E Invalid userid - userid<br />

H<strong>CP</strong>20E Userid missing or invalid<br />

H<strong>CP</strong>26E Oper<strong>and</strong> missing or invalid<br />

H<strong>CP</strong>45E userid not logged on<br />

1384 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong><br />

USER userid: RELATIVE SHARE = nnnnn [; m DEDICATED <strong>CP</strong>U[S]]<br />

MAXIMUM SHARE = option type value<br />

is issued when the comm<strong>and</strong> completes successfully. The string m DEDICATED<br />

<strong>CP</strong>U[S] only appears if the user has real processors dedicated to his or her virtual<br />

<strong>CP</strong>U or <strong>CP</strong>Us.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!