ADSM-L

Re: TSM -Error ANR9999D mmsscsi.c(4318): Element address mis

2000-04-10 05:16:47
Subject: Re: TSM -Error ANR9999D mmsscsi.c(4318): Element address mis
From: Harald Wassmann <harald.wassmann.hw AT BAYER-AG DOT DE>
Date: Mon, 10 Apr 2000 11:16:47 +0200
lipp AT STORSOL DOT COM@INTERNET AT VM.MARIST DOT EDU on 04/05/2000 16:53:26
Bitte antworten an lipp AT storsol DOT com@INTERNET
Gesendet von: ADSM-L AT VM.MARIST DOT EDU

An: ADSM-L AT VM.MARIST DOT EDU@INTERNET
Kopie:
Thema: Re: TSM -Error ANR9999D mmsscsi.c(4318): Element address mis
Hi Kelly,

thanks for responding. The lbtest utility tells me the drive has element
number 2. This is exactly the element I used to define the drive in TSM.

The point confusing me is, everything works fine with ADSM but not with TSM,
some other
hardware devices work and replacing the TSM scsidriver by the ADSM scsidriver
seems to fix it.
I got no further ideas. I think'll try to open a problem report to Tivoli
Support.


Thanks

Harald
harald.wassmann.hw AT bayer-ag DOT de



-----Original Message-----
You should use the lbtest utility in the utils directory.  The syntax is:
You should use the lbtest utility in the utils directory.  The syntax is:

lbtest -dev lb0.0.0.1 (or whatever the address is for your library)

Then select manual test, open (6), return element count (8) and return all
library inventory (9).  This will scroll by fast so you might want to have
your window properties set to scroll.   Then look for the drive entries at
the very top and verify that you have the correct element number for the
correct scsi id.

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

<Prev in Thread] Current Thread [Next in Thread>
  • Re: TSM -Error ANR9999D mmsscsi.c(4318): Element address mis, Harald Wassmann <=