It is supposed to have priority over everything and this was the line I
got when I gave up and called into support the other night.  They asked
me for a bunch of info and then came back with some song and dance about
how it only works that way with tape drives.  I'm running opticals.
They had two suggestions.  1) Increase the size of my recovery log which
I can do, though I've been doing that for weeks and my recovery log will
soon be the size of my database (well, not soon, but soon enough) or 2)
Write scripts that poll for two active (drive requiring processes) when
I need a dbbackup and then stop one so the dbbackup can use a drive.

I asked for documentation to this effect because originally I was told
that this occurance showed that the product doesn't meet specs here.
I've worked in R & D and I find it difficult to believe that there is
one set of rules for tapes and another for optical drives.  Even so, I'm
going to make some noise about their modifying their specs if they do
address the devices differently.

Hilary Whitehead
IBM Global Services

> -----Original Message-----
> From: Matthew Emmerton [SMTP:Matthew_Emmerton AT agorainc DOT net]
> Sent: Thursday, June 04, 1998 2:40 PM
> To:   HWhitehead AT CAISO DOT COM
> Subject:      RE: Roll Forward
>
>
> -----Original Message-----
> From:   HWhitehead AT CAISO DOT COM
> Sent:   Thursday, June 04, 1998 2:19 PM
> To:     ADSM-L AT VM.MARIST DOT EDU
> Subject:        Roll Forward
>
> Therefore, no drive = no backup  = full recovery log = dsmserv crash.
> I
> thought that this RL backup was supposed to have prriority over other
> processes.
>
>
> Are you sure that you've got your priority settings right?  Under
> ADSM, a
> priority 5 is higher than a priority 1 (contrary to popular
> convention.).
>
> --
> Matthew Emmerton, System Administration
> Agora Food Merchants, National IT
> +1 (905) 565-4231
>
>