Having a lot of HSM activities, our scheduled backup client's are often
terminated:

actlog:

01/26/97   07:29:48  ANR0400I Session 6656 started for node HYDRA_C (SunOS).
                     ....
01/26/97   10:59:51  ANR0492I All drives in use. Session 6656 for node HYDRA_C
                      (SunOS) being preempted by higher priority operation.
01/26/97   10:59:51  ANR0490I Canceling session 6656 for node HYDRA_C (SunOS) .
01/26/97   10:59:51  ANR0487W Session 6656 for node HYDRA_C (SunOS) terminated
                      - preempted by another operation.

dsmsched.log:

01/26/1997 11:02:01 ANS4017E Session rejected: TCP/IP connection failure
01/26/1997 11:02:01 ANS4847E Scheduled event 'DAILY_HYDRA' failed.  Return code 
= 1.
01/26/1997 11:02:01 Sending results for scheduled event 'DAILY_HYDRA'.
01/26/1997 11:02:02 ANS4029E Session rejected: Communications protocol error

Question: is there a mechanism to prevent backup's kicked off by higher
          priority operations? Something like a wait mechanism instead of this
          terminating mechanism?

Btw, our mountlimit = 4.

(running ADSM V2.1.0.9 on a SP2 (AIX 4.1.4.0) using 3494 with 4 3590 drives,
 backup/archive client's 2.1.0.5 & 2.1.0.6 on AIX 3.2, AIX 4.1.4, SunOs,
 Solaris, SGI, HSM client 2.1.0.5 on AIX 4.1.4.0)

Regards,

Henk ten Have                   SARA, Academic Computing Services Amsterdam
Systems Programmer              Kruislaan 415
E-mail: hthta AT sara DOT nl           1098 SJ Amsterdam
Phone : +31205923000            The Netherlands