Hi all,

Recently we've started seeing these messages pop up when we try to run
our nightly db2 backup:

03/10/2005 02:24:25   ANR8337I LTO volume 000002L2 mounted in drive
DRIVE0
 AM                    (/dev/IBMtape0).

03/10/2005 02:33:49   ANR8341I End-of-volume reached for LTO volume
000002L2.
 AM

03/10/2005 02:33:51   ANR9999D pvrntp.c(2541): ThreadId<18> NtpOpFlush
error on
 AM                    drive DRIVE0 (/dev/IBMtape0); already reached
EOV once.
                       Callchain of previous message: 0x08793053
outDiagf+0x203
                       <- 0x08857b37  NtpFlush+0x1d7 <- 0x0885793e
NtpWrite+0x
                       50e <- 0x08867533  LtoWrite+0x83 <- 0x084c7c5f

                       AgentThread+0x93f <- 0x0809c53f
StartThread+0x8f <-
                       0xb759bdac  *UNKNOWN* <- 0xb7537a8a  *UNKNOWN*
<-
03/10/2005 02:33:51   ANR1411W Access mode for volume 000002L2 now set
to
 AM                    "read-only" due to write error.

03/10/2005 02:33:51   ANR0523W Transaction failed for session 5072 for
node
 AM                    ELMSDB (DB2/LINUX) - error on output storage
device.
03/10/2005 02:33:54   ANR0403I Session 5072 ended for node ELMSDB
(DB2/LINUX).
 AM


Now if we update the access on the tape to readwrite and use db2adutl to
delete a few of the backups, everything is fine but the tape library is
a 3582 LTO2 and there are PLENTY of scratch volumes. Shouldn't TSM just
use another tape?

We're running TSM Version 5, Release 2, Level 2.0 on RHEL 3.0 and DB2 is
running DB2 8.1FP4.

Thanks for any help!
John E. Vincent