Re: problem with 3494 library after TSM upgrade from 3.7.4 to 4. .2.1.7

2002-01-21 Thread Dennis Glover
Hello, We had some problems after upgrading to TSM 4.2.1.7 and subsequently TSM 4.2.1.9, and although the problems were 3not precisely the same as yours, I might offer some insight. Our problem turned out to be that TSM 4.2.x.y could not append to tapes which had originally been written by ADSM

Re: problem with 3494 library after TSM upgrade from 3.7.4 to 4. .2.1.7

2002-01-21 Thread Dennis Glover
Hello again, I read a little further into the digest, and noted that someone recommended "upgrading the microcode" (IBM-ese for flashing the PROM?) in your 3590 drives. This was one of the steps we took, and it probably helped. We also upgraded the IBMtape and lmcpd packages (Sun analogues for

Re: problem with 3494 library after TSM upgrade from 3.7.4 to 4. .2.1.7

2002-01-20 Thread Seay, Paul
? -Original Message- From: Steve Roder [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 20, 2002 1:16 PM To: [EMAIL PROTECTED] Subject: Re: problem with 3494 library after TSM upgrade from 3.7.4 to 4..2.1.7 I would delete the drive and library defintions, and redefine them to TSM. If they define ok

Re: problem with 3494 library after TSM upgrade from 3.7.4 to 4..2.1.7

2002-01-20 Thread Steve Roder
I would delete the drive and library defintions, and redefine them to TSM. If they define ok, them checkin your scratch tapes, followed by the private tapes. If you cannot redefine the library and drives, then I would look at upgrading atape and atldd, and removing the devices from the ODM, and r