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.

eee[%]<br />

is the percentage of paging exposures the scheduler is to view when<br />

considering adding a loading E2 or E3 user to the dispatch list. If the<br />

number of Q2 <strong>and</strong> Q3 loading users currently in the dispatch list plus<br />

the loading E2 or E3 user under consideration exceeds the eee<br />

percentage of paging exposures, the user may not be added<br />

immediately <strong>and</strong> is delayed further.<br />

fff[%] is the percentage of paging exposures the scheduler should view when<br />

considering adding a loading E3 user to the dispatch list. If the number<br />

of Q3 loading users currently in the dispatch list plus the loading E3<br />

user under consideration exceeds the fff percentage of paging<br />

exposures, the user may not be added immediately <strong>and</strong> is delayed<br />

further.<br />

Note that in order to enter the dispatch list, an E1 user must only pass the one<br />

barrier established by ddd. But an E2 user must pass the two barriers set by<br />

ddd <strong>and</strong> eee. And an E3 user must pass the three barriers set by ddd, eee, <strong>and</strong><br />

fff. This is exactly analogous to the operation of STORBUF, though STORBUF<br />

was explained differently. Similarly, the differences between the values (ddd-eee<br />

<strong>and</strong> eee-fff) represent LDUBUF buffers (for Q1 <strong>and</strong> Q2 respectively), just as<br />

they do for STORBUF.<br />

In each case, the LDUBUF values must be in the range 0 through 999, with a<br />

restriction that ddd ≥ eee ≥ fff. Any value greater than 100 represents an<br />

overcommitment of DASD paging capacity.<br />

LDUBuf INITial<br />

sets the percentage parameters back to their initial values, 100%, 75%, <strong>and</strong><br />

60%.<br />

DSPBuf {iiiii jjjjj kkkkk}<br />

gives the scheduler criteria for admitting users to the dispatch list in cases of<br />

users who are not prevented from entering by the more resource-specific<br />

barriers established by STORBUF <strong>and</strong> LDUBUF. DSPBUF st<strong>and</strong>s for “dispatch<br />

buffer” <strong>and</strong> refers to the total number of users (by class) that are allowed in the<br />

dispatch list.<br />

The oper<strong>and</strong> iiiii refers to the number of openings in the dispatch list made<br />

available to users with short-running (E1) transactions. A subset, jjjjj, of the iiiii<br />

openings is also made available to users with medium-length transactions; the<br />

E1 <strong>and</strong> E2 users compete for these slots. Another subset, kkkkk, of the jjjjj<br />

openings is also made available to users with long-running transactions; the E1,<br />

E2, <strong>and</strong> E3 users all compete for these slots. QUICKDSP <strong>and</strong> other E0 users<br />

are not limited by these numbers <strong>and</strong> may enter the dispatch list without limit.<br />

The valid range of values is 1 to 32767 where iiiii ≥ jjjjj ≥ kkkkk<br />

Example: dspbuf 35 30 18<br />

SET SRM<br />

35 openings are available to E1 users, but only 5 of them (5 = 35 − 30) are<br />

exclusively available to E1 <strong>and</strong> are guaranteed not to be already occupied by<br />

E2 <strong>and</strong> E3 users.<br />

30 openings are available to E2 users, but only 12 of them (12 = 30 − 18) are<br />

guaranteed not to be already occupied by E3 users. None of the 30 openings is<br />

guaranteed against occupation by E1 users; however, E1 users generally get<br />

out of the way quickly.<br />

Chapter 2. <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> 1393

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

Saved successfully!

Ooh no, something went wrong!