Thomas, This sounds like a recurring "bug"; did you try adjusting IDLETIMEOUT in dsmserv.opt?
Alternatively, could you identify the session holding the tape (via q se f=d)??? If so, then you can at least cancel the offending session (should be in idle-wait, anyway). Did Level 2 give you any help? Regards, Don Don France Technical Architect - Tivoli Certified Consultant Professional Association of Contract Employees (P.A.C.E.) San Jose, CA (408) 257-3037 [EMAIL PROTECTED] ----- Original Message ----- From: "Thomas Denier" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 27, 2002 1:37 PM Subject: Tape retention after restores > We have been seeing a recurrent problem with GUI restores under Windows NT. > A system administrator will start a restore and walk away from his disk. > When the restore finishes, the session will stay open and the last tape > used in the restore will remain mounted. We have sometimes had a tape drive > tied up for hours before getting the person who started the restore to > respond to a telephone call or a page. We have occasionally seen a similar > problem with command line restores under HP-UX. A batch mode dsmc restore > will relinquish the tape drive when the restore ends, but a restore run > from a loop mode dsmc session will not. Our server runs under OS/390 and > is currently at level 4.2.1.9. The last Windows NT client to monopolize a > tape drive was at level 4.1.2.12. The last HP-UX client to do so was at > level 4.1.2.0. Is there any way to get TSM to take a more rational > approach to tape drive retention in this situation?
