In some past posts, while discussing about WLM, someone introduced 'skip
clock' concept to describe behaviour of wlm when goals are not reached,
for
instance because they are quite high and there isn't enough to boost them.
In this case wlm ignores them (or leaves them with reached velocity) until
skip clock expires (so I was told).
Is this skip clock concept described somewhere (manuals, papers ) ?
From the WLM Services:
"They are also skipped when a potential receiver's skip clock hasn't
expired. If a receiver is assessed and all actions to help it are rejected,
a skip clock (counter) is set and the service class period will not be
selected as a receiver again until the skip clock expires."
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
