(Cross posted)
Esteemed listers
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
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
On Wed, 9 Jul 2008 08:12:39 -0500, Max Scarpa [EMAIL PROTECTED]
wrote:
(Cross posted)
Esteemed listers
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
Hi Adam
I've found it, thank you very much
Max Scarpa
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at
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
Hi Mark, thank you for your reply
I read it in redbook as well but as you said there's no 'direct' reference
to skip clock concept, only a generic delay (skip) as it was considered
useless to help that workload due to unattainable goals.
Best regards
Max Scarpa
6 matches
Mail list logo