Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error defining 3590 library

107 views
Skip to first unread message

Marc Layne

unread,
Feb 3, 2000, 3:00:00 AM2/3/00
to
Hi all
I am getting the following error when trying to define an 3590 automated
(SCSI) library. I have checked the system cansee the device (/dev/rmtx)
and i am able to tar to the devices so no problem there.
Versions: TSM 3.7.0
AIX version 4.3.2
Tape : 3590 B11
Has anyone seen this before...
All help greatly appreciated....


Date/Time Message

--------------------
----------------------------------------------------------
020300 12:12:18 ANR8300E I/O error on library 3590LIB1
(OP=00006C06,
CC=207, KEY=FF, ASC=FF, ASCQ=FF, SENSE=**NONE**,

Description=Device is not in a state capable of

performing request). Refer to Appendix B in the

'Messages' manual for recommended action.

020300 12:12:18 ANR8418E DEFINE LIBRARY: An I/O error occurred
while
accessing library 3590LIB1.

020300 12:16:18 ANR8300E I/O error on library 3590LIB1
(OP=00006C06,
CC=207, KEY=FF, ASC=FF, ASCQ=FF, SENSE=**NONE**,

Description=Device is not in a state capable of

performing request). Refer to Appendix B in the

'Messages' manual for recommended action.

020300 12:16:18 ANR8418E DEFINE LIBRARY: An I/O error occurred
while
accessing library 3590LIB1.

020300 13:11:33 ANR8300E I/O error on library 3590LIB1
(OP=00006C06,
CC=207, KEY=FF, ASC=FF, ASCQ=FF, SENSE=**NONE**,

Description=Device is not in a state capable of

performing request). Refer to Appendix B in the

'Messages' manual for recommended action.

020300 13:11:33 ANR8418E DEFINE LIBRARY: An I/O error occurred
while
accessing library 3590LIB1.

020300 13:11:51 ANR2017I Administrator ADMIN issued command: QUERY
ACTLOG
s=error

Marc Anthony Layne

RS/6000 Product Manager
Faritec (Pty) Ltd.
Mail to: mla...@faritec.co.za
Tel: +27 21 7629702 Mobile: +27 82 4169086
Fax: +27 21 7629737
"You only live once.. but if you do it right once is enough...."

Kelly Lipp

unread,
Feb 3, 2000, 3:00:00 AM2/3/00
to
I haven't done this in a long while, but you should use smit to take a look
at the ADSM devices. Perhaps you are not providing ADSM with the correct
device in the definition.

Bill, jump in here and save the Unix challenged!

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80919
(719)531-5926
Fax: (719)260-5991
www.storsol.com
li...@storsol.com

Long, Matt

unread,
Feb 3, 2000, 3:00:00 AM2/3/00
to
Marc,

It probabaly means the device is either still busy for some reason
or someone power cycled the ATL and it is not properly talking to the ADSM
database now. You might want to restart ADSM and or reboot your server
depending upon what state the library is in. You may also want to recreate
your device as well if you have made any changes to the software and or
hardware. I have had the same issues as well. Thanks

Matt

0 new messages