On previous versions of ADSM 3.x, we used to see a few deadlocks from
expiry colliding with other processes.  Sometimes expiration would be
cancelled, sometimes the other process would be cancelled.

More annoying was that expiration could lock out other processes and
even queries for long long periods of time.

Under 3.1.2.40 (& Solaris) I have not seen either of these happen
again.  Our expiration runs for in excess of 48 hours (45 million
objects to consider.)


Russell


[Charset iso-8859-1 unsupported, filtering to ASCII...]
> Hi
>
> We are running Server 3.1.2.20 on AIX 4.1.5 and we see exactly the same
> errors occurring when running Database backups and expiration at the same
> time.
>
> Grant Cohn
>
> -----Original Message-----
> From: Winfried Heilmann [mailto:Winfried.Heilmann AT INFRACOR DOT DE]
> Sent: Thursday, August 26, 1999 09:47
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: running backup + expire at the same time
>
>
> Hi,
> I have read in several mails that problems may occur, when migration- ,
> backup
> and reclamation processes are running at the same time.  ( I also have
> problems with deadlocks, and IBM told me too to start expire and backup at
> different times) But I have not found any documentation where this is
> discribed. The scheduler of ADSM doesn't  support the definition of
> dependencies, so I only have the chance to start the processes at different
> times. This is not  a good solution.
>
> IBM should document which procceses are allowed to run at the same time and
> the
> scheduler should support  dependencies or resource-controlling like other
> schedulers (OPC or control m).
>
> What are you thinking about that?
>
> regards winfried