What is your schedule randomization set to? This takes precedence for
schedmode=polling.
Al
Alan Davenport
Senior Storage Administrator
Selective Insurance
[EMAIL PROTECTED]
(973) 948-1306
HELP SET RANDOMIZE
SET RANDOMIZE
SET RANDOMIZE (Set Randomization of Scheduled Start Times)
Use this command to set randomized start times within the startup window of
each schedule for clients using the client-polling scheduling mode. A
startup window is the start time and duration during which a schedule must
be initiated. A client-polling scheduling mode is a client/server
communication technique where the client queries the server for work. Each
schedule has a window during which execution can begin. To balance network
and server load, the start times for clients can be scattered across that
window. Use this command to specify the fraction of the window over which
start times for clients are to be distributed.
The randomization occurs at the beginning of the window to allow time for
retries, if necessary, unless the client's first contact with the server is
after the start time for the event.
You can issue the QUERY STATUS command to display the value for the schedule
randomization percentage. At installation, the value is set to 25 percent.
Set the randomization percentage to a value greater than 0 to prevent
communication errors that can result from a large group of clients
contacting the server simultaneously. If you do experience communication
errors, you can increase the randomization percentage so that client contact
is spread out, thus decreasing the chance for communication overload and
failure.
Privilege Class
To perform this task, you must have system privilege.
Syntax
>>-Set RANDomize--percent--------------------------------------><
Parameters
percent (Required)
Specifies the percentage of the startup window over which the start
times for individual clients are distributed. You can specify an
integer from 0 to 50.
A value of 0 indicates that no randomization occurs and that all
clients execute schedules at the beginning of the startup windows.
A value of 50 indicates that clients are assigned start times that are
randomly scattered across the first half of each startup window.
At installation, this value is set to 25, indicating that the first 25
percent of the window is used for randomization.
If you have specified DURUNITS=INDEFINITE in the DEFINE SCHEDULE
command, the percentage is applied to a 24 hour period. For example, a
value of 25 percent would result in a 6 hour window.
Examples
Task
Set randomization to 50 percent.
Command:
set randomize 50
Related Commands
Table 238. Commands Related to SET RANDOMIZE
Command Description
DEFINE SCHEDULE Defines a schedule for a client
operation or an administrative
command.
QUERY STATUS Displays the settings of server
parameters, such as those selected by
the SET commands.
SET SCHEDMODES Specifies the central scheduling mode
for the server.
-----Original Message-----
From: Mark Bertrand [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 14, 2002 10:15 AM
To: [EMAIL PROTECTED]
Subject: Re: schedmode polling and immediate client actions
I have a similar question, I thought by stopping the scheduler service on
the client that it would then poll. I think it is because I see the entry in
the sched.log file. The problem is it's not immediate, the logs show that
the job will start in 1 hour 20 minutes. So I restarted the client schedule
again. The log now says the job will start in 45 minutes. So I restarted the
client service again, it now says it will start in 52 minutes. At this point
I though I should stop while I was ahead.
Does anyone know why the wait time had changed since I had changed the
schedule to run NOW?
Thanks,
Mark Bertrand
-----Original Message-----
From: Joseph Seigh [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 14, 2002 3:57 AM
To: [EMAIL PROTECTED]
Subject: Re: schedmode polling and immediate client actions
Quoting Karel Bos <[EMAIL PROTECTED]>:
> Hi,
>
> We have changed our scheduling mode from prompted to polling. Scheduled
> back-ups run fine. The immediate client schedule won't run. The status of
> the immediate schedule turns to pending and will not function.
>
>
It will run as soon as your client polls for schedules. If your
client poll interval is 4 hours, then on average you will wait
2 hours for an immediate schedule to run.
Joe Seigh
