That is not the behavior I've seen...

If for some reason a scratch tape fails a mount (like it can't read the
internal label) what I've seen in the activity log is an error message that
states "~~~ volser xxxxx being set to PRIVATE to prevent further access ~~~~
"

I don't have the specific message number but I have seen it in the past in
my AIX server environments with 3494 ATL's & 3590 drives.

Dwight E. Cook
Software Application Engineer III
Science Applications International Corporation
509 S. Boston Ave.  Suite 220
Tulsa, Oklahoma 74103-4606
Office (918) 732-7109



-----Original Message-----
From: Gerhard Rentschler [mailto:g.rentschler AT RUS.UNI-STUTTGART DOT DE]
Sent: Monday, August 05, 2002 7:44 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Defective Scratch Tapes


Hello,
what happens if a scratch can't be mounted in the drive for some reason
(e.g. because it is write protected)? A colleague just told me that in this
case the TSM server tries to mount the same tape over and over again. Is
this true?
In table libvolumes there is no field for an error flag.
Best regards
Gerhard

---
Gerhard Rentschler            email:g.rentschler AT rus.uni-stuttgart DOT de
Regional Computing Center     tel.   ++49/711/685 5806
University of Stuttgart       fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany