Thanks,

I also find a technote (BKI5008E, ANS1017E RC -50, and ANR0487W reported during 
DP for mySAP backup) about the subject, suggesting to add NOPREEMPT option in 
dsmserv.opt...

And in technote IY02629, it state "To provide the requested additional 
information in ANR0487W
would require a design change to the Server code. As such
this APAR is being closed SUG."

"immutably" ? It's a design choice but why this choice ? 
Is it so difficult to manage some kind of "job queue" ?

Pierre

> -----Message d'origine-----
> De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De 
> la part de Richard Sims
> Envoyé : jeudi 20 septembre 2007 14:39
> À : ADSM-L AT VM.MARIST DOT EDU
> Objet : Re: [ADSM-L] ANR0487W
> 
> On Sep 20, 2007, at 7:53 AM, CAYE PIERRE wrote:
> 
> > Hello,
> >
> > I am facing a dead backup with msgno ANR0487W...
> >
> > -----------
> > ANR0487W Session session number for node node name (client
> > platform) terminated - preempted by another operation.
> ,,,
> 
> Unfortunately, the product lacks any way to assign a 
> preemption- governing priority to sessions: the preemption 
> scheme is immutably hard-coded into the architecture.  See 
> "Preemption of Client or Server Operations" in the Admin 
> Guide manual for an overview, and the one option you have to 
> prevent preemption of backups.
> 
>     Richard Sims  at Boston University
>