Change schedmode to prompted on the client and restart the scheduler.

With schedmode polling the start of schedule is dependent on the randomization 
setting on the TSM server (q sys).





-----Original Message-----
From: Cecily Hewlett [mailto:chewlett AT ZA.SAFMARINE DOT COM]
Sent: vrijdag 5 maart 2004 10:09
To: ADSM-L AT VM.MARIST DOT EDU
Subject: / /OREF:CPT18245 Tsm Scheduler


I need with my tsm scheduler.  It seems to be wasting alot of time...

I am running TSM 5.1.6 across  fibre,  with 8 clients backing up to a
3583 LTO with 2 drives on a SAN.

I stop and start my client schedulers & the storage agents from cron.

Often a scheduled event, which is due to start at 15:00 will only
begin at 16:30 - despite the fact that it is the first scheduled
event of the day and  is not waiting for drives or resources.

Here are my some settings taken from the dsm.sys on the client:

         errorlogretention 10,D
         PASSWORDACCESS GENERATE
         nodename        sapdev
         schedmode       polling
         schedlogname    /usr/tivoli/tsm/logs/dsmsched.log
         schedlogretention 4,D
         maxcmdretries  3
         retryperiod    10
         queryschedperiod 1


Can anyone help?

Cecily Hewlett
AIX and TSM Administrator
Cape Town