That was the problem. I found the APAR and with the SHOW LIBRARY command I
was able to see the 349x information go away after doing an UPD DRIVE
command. When I bounced TSM, the 349x information was present. Also after a
DEL DRIVE and DEF DRIVE command it was back.
Also turns out I was the start of the probem. Over the weekend we had a tape
get stuck in the RMT0 drive. I was at home monitorring the installation of
the new drives, so I just UPD DRIVE ONLINE=NO until I came in on monday to
clear the drive. Then an UPD DRIVE ONLINE=YES and the thing stopped working.
My CE is a little pissed at me right now. I just had him check all the SCSI
connections, library definitions and run diags on the drive. Only to find
out it was a software problem. :-)
Thanks,
Bill
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Malbrough, Demetrius
Sent: Thursday, February 15, 2001 11:36 AM
To: [EMAIL PROTECTED]
Subject: Re: ANR8301E I/O error on 3494 library - kinda urgent!
This seems to be your problem Bill:
APAR= IC27477
ISSUING THE UPDATE DRIVE COMMAND WITHOUT SPECIFYING THE DEVICE NAME IN THE
COMMAND COULD CAUSE 3494 TO LOSE DRIVE INFORMATION
Status: CLOSED Closed: 07/25/00
Error Description:
Issuing the UPDATE DRIVE command without specifying the device name in the
command, could cause the 3494 library manager to lose the information for
this drive. As a result, any subsequent attempts by the TSM Server to
access this drive may fail with the following errors:
.
ANR8301E I/O error on library 3494 (OP=005C6D37, SENSE=N/A,
CC=00000023).
ANR8848W Drive DRIVE1 of library 3494 is inaccessible; server has begun
polling drive.
.
The 3494 library manager assigns a device number to each drive and issuing
the UPDATE DRIVE command without specifying the device name for that drive
(i.e. device=/dev/rmt1) may cause the the existing device number assigned to
that drive by the 3494 to be modified or deleted. The completion code of 23
in the error message above indicates that the device does not exist in the
library. In order to recover from this condition the user must delete and
redefine the drive to TSM, or recycle the TSM Server.
.
This problem exists in the 3.1.x and 3.7.x Server code, but only affects
drives in a 3494 library.
Local Fix:
Include the device parameter when issuing the UPDATE DRIVE
command.
Correct syntax:
UPDATE DRIVE 3494LIB DRIVE1 device=/dev/rmt1 ONLINE=YES
Incorrect syntax:
UPDATE DRIVE 3494LIB DRIVE1 ONLINE=YES
Problem Summary:
****************************************************************
* USERS AFFECTED: *
ADSM 3.1.2.X and TSM 3.7X customers on the AIX, HP, SUN and
NT platforms using 3494 libraries.
****************************************************************
* PROBLEM DESCRIPTION: *
After an UPDATE DRIVE command without the DEVICE parameter,
the TSM server looses the device number for the given drive.
The TSM server needs that device number to specify the
drive when communicating to the 3494 Library Manager.
The TSM server may abend when attempting to communicate to the
3494 Library Manager to perform a mount/demount activity or to
obtain information about the given drive. Otherwise, there
may be I/O errors in the activity log; that is, ANR8301E
messages with a completion code of 0x023.
****************************************************************
* RECOMMENDATION: *
Apply PTF when available.
****************************************************************
The TSM server maintains the correct device number for
the given drive after an UPDATE DRIVE command whether
or not the DEVICE parameter was specified.
Temporary Fix:
Until the fix is available:
1) Include the DEVICE parameter in the UPDATE DRIVE command.
2) Delete and then re-define the drive to TSM.
Comments:
MODULES/MACROS: NONE
Problem Conclusion:
None.
-----Original Message-----
From: William Boyer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 15, 2001 9:02 AM
To: [EMAIL PROTECTED]
Subject: ANR8301E I/O error on 3494 library - kinda urgent!
AIX 4.3
TSM 3.7.3.0
IBM 3494
3590E1A's (4)
Last weekend we added 2 addititional 3590E's to our library. We also added
more SCSI controllers to the RS/6000 to support them. Right now I have 1
SCSI controller to 1 3590E drive. Nothing is chained. In preparation for
this, I deleted all the drives from the library in TSM, halted TSM, then
rmdev'd the existing /dev/rmtx's.
When everything was back up, cfgmgr found the drives, each on it's own
controller. I added them back in to TSM (def drive 3494 RMTx
device=/dev/rmtx). When I try to mount a tape in the /dev/rmt0 drive, I get
the following error:
ANR8301E I/O error on library 3494 (OP=005C6D37, SENSE=N/A, CC=00000023).
ANR8301E I/O error on library 3494 (OP=005C6D37, SENSE=N/A, CC=00000023).
and the drive goes into a polling state. To test this out, I halted TSM and
using the mtlib command I was able to successfully mount a tape in each of
the drives. I'm assuming this is telling me that it's now a hardware
problem, or a problem with the ATLDD or ATAPE (which are both at the latest
releases).
I have my CE here today, but he's kind of at a loss, too.
Does anyone have any ideas? Or maybe where I could look up these OP and CC
codes?
TIA,
Bill Boyer
"Growing old is mandatory, growing up is optional." - ???
