ADSM-L

Schedule randomization

1997-04-28 12:06:23
Subject: Schedule randomization
From: Tom Brooks <tbrooks AT VNET.IBM DOT COM>
Date: Mon, 28 Apr 1997 09:06:23 PDT
Tom, to some extent what you are saying is true. It goes a little
deeper. For all nodes associated with a given schedule the node most
recently registered is likely to be the first one to run under
randomization. The way to get around this is:
 For nodes that need to start early in the randomization window, copy
the existing schedule and set a higher priority for the new schedule
with 1 being the highest priority and 10 being the lowest. The default is
5.
 Then remove the association for the related node(s) from the old schedule and
associate it with new.

Use the UPDATE SCHEDULE to change the priority after COPYing the old schedule.

Tom Brooks
ADSM Development
<Prev in Thread] Current Thread [Next in Thread>