A quick look at past activity logs indicates this began the first day of production after the 3590E drive upgrades.
This had required a newer version of Atape; would this have changed how messages are passed back to ADSM? Thanks, Mike. >Mike, > > I found the same issue. It can be reproduced on ADSM version 3 and >4.1. I do not think it is limited to 3590E drives though. Tivoli people, >have you found a solution to this problem yet? > >Jeff Bach > >> -----Original Message----- >> From: Mike Crawford [SMTP:[EMAIL PROTECTED]] >> Sent: Wednesday, February 06, 2002 12:39 PM >> To: [EMAIL PROTECTED] >> Subject: No Drives Available errors >> >> Good morning, >> >> Since we upgraded our 3590B's to 3590E's, whenever all the drives in the >> library >> are full, we get these errors, under ADSM 3.1, AIX: >> >> 02/06/2002 11:13:43 ANR8447E No drives are currently available in library >> MAGSTOR1. >> >> >> >> This causes restore/retrieves to fail, rather than queue, until a drive >> becomes >> available. We are still using the save devclass definitions from before, >> MOUNTLIMIT=5 >> (we have five drives in the 3494.) >> >> Is there some other setting that needs to change? >> >> Thanks, >> Mike > > >********************************************************************** >This email and any files transmitted with it are confidential >and intended solely for the individual or entity to >whom they are addressed. If you have received this email >in error destroy it immediately. >********************************************************************** >
