It would certainly help to see some more specifics. For example, the dsmsched.log file for one of the clients in question that did not kick off when expected, just to verify that, for sure, it is using prompted scheduling; and the activity log from the scheduled start time and on, to see what the server was doing, as well as other things like the client dsm.opt file for the aforementioned client, and the client option set definition for that client.
Server-side randomization has no effect on prompted scheduling. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 2006-04-17 22:13:06: > I'm trying to remember what it is about a backup schedule that, even though > scheduled for say 8PM, does not kick off right away, nodes show pending for > some time. I've been comparing the 5.2 and 5.3 server settings but can't > find any obvious differences, yet the 5.2 server kicks off each schedule > right at the specific time whereas the 5.3 server I'm putting up does not. > > > > I have a clopt set that has schedmode as prompted, which is the same on both > servers and scheduling modes is set to any, same on both servers. > > > > What am I missing that I thought I'd taken care of? I'd actually prefer to > have these guys start right away. > > > > Thanks, > > > > Geoff Gill > > TSM Administrator > > PeopleSoft Sr. Systems Administrator > > SAIC M/S-G1b > > (858)826-4062 > > Email: <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
