John

We found that the behaviour of admin schedules changed when we upgraded from
3.7.2 to 3.7.4.

Our TSM servers have a number of long-running scripts initiated by admin
schedules - eg backing up a disk storage pool to an offsite tapepool via
server-to-server comms before initiating a migration of the disk storage pool to
local tape. We specify WAIT=YES on the backup command to ensure correct
sequencing.

As you observed, in 3.7.2 an admin schedule in progress will cause a subsequent
one to miss if the first hasn't finished by the time the second one is due to
start.

It came as a complete surprise to us when we upgraded to 3.7.4 that this was no
longer the case. It is now possible to have multiple admin schedules running in
parallel.

Neil




The information in this e-mail is confidential and may also be legally
privileged. The contents are intended for recipient only and are subject
to the legal notice available at http://www.keldagroup.com/email.htm
Yorkshire Water Services Limited
Registered Office Western House Halifax Road Bradford BD6 2SZ
Registered in England and Wales No 2366682