ADSM-L

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

2015-10-04 17:31:35
Subject: TSM -Error ANR9999D mmsscsi.c(4318): Element address mismatc
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
To: ADSM-L AT VM.MARIST DOT EDU
Hello all,

we are planing to migrate from ADSM to TSM. Im stuck in the evaluation
process
cause I can't get my test equipment working. Everytime I use commands on TSM
concering the DLT Library (audit libr, checkin libv, label libv), I get an
error message that there is an element address mismatch and the process
stops.

04/05/2000 16:18:50  ANR2017I Administrator ADMIN issued command: CHECKIN
                      libvol DLTLIB search=yes status=private
04/05/2000 16:18:50  ANR0984I Process 4 for CHECKIN LIBVOLUME started in the
                      BACKGROUND at 16:18:50.
04/05/2000 16:18:50  ANR8422I CHECKIN LIBVOLUME: Operation for library
DLTLIB
                      started as process 4.
04/05/2000 16:18:50  ANR9999D mmsscsi.c(4318): Element address mismatch;
                      slotInfo.elem = 7, slotInv.addr = 0
04/05/2000 16:18:50  ANR8832E CHECKIN LIBVOLUME for volumes in search mode
in
                      library DLTLIB failed.
04/05/2000 16:18:50  ANR0985I Process 4 for CHECKIN LIBVOLUME running in the
                      BACKGROUND completed with completion state FAILURE at
                      16:18:50.

This errors only occur when I use an ADIC VS DLT 400 Library (ADIC
autochanger
device - firmware revision 0236
 with one Quantum DLT 4000 drive - firmware D069). If I use an Compaq 4mm
Dat
Changer everything works.

As TSM is installed on an Windows NT 4.0 SP5 Server, I replaced the
adsmscsi.sys file that comes with TSM by the old adsmscsi.sys
file form adsm 3.1.2.42. After rebooting the server  the error is gone. But
I
think that can't be the solution, cause we are planing to test the
SAN features of TSM and therefor the original TSM-asdmscsi.sys driver might
be
necessary.

What I've testet so far:
ADSM 3.1.2.42 with DLT Library with the old adsmscsi.sys        okay

ADSM 3.1.2.42 updated to TSM 3.7.0.0 with DLT Library with TSM
adsmscsi.sys       the error occurs
ADSM 3.1.2.42 updated to TSM 3.7.0.0 updated to TSM 3.7.2.0 with DLT Library
with TSM adsmscsi.sys       the error occurs

ADSM 3.1.2.42 updated to TSM 3.7.0.0 updated to TSM 3.7.2.0 with DLT Library
with the old adsmscsi.sys        okay

Fresh Win NT installation with fresh installed TSM 3.7.0.0 with DLT Library
with TSM adsmscsi.sys        the error occurs
Fresh Win NT installation with fresh installed TSM 3.7.0.0 updated to TSM
3.7.2.0 with DLT Library with TSM adsmscsi.sys       the error occurs
Fresh Win NT installation with fresh installed TSM 3.7.0.0 updated to TSM
3.7.2.0 with DLT Library wiht the old adsmscsi.sys    okay

Fresh NT installation with fresh installed TSM 3.7.0.0 updated to TSM
3.7.2.0
with Compaq 4mm DAT  with TSM adsmscsi.sys    okay


When I updated from ADSM to TSM (using the TSM adsmscsi.sys) with some Tape
checked in the library by ADSM these Library
volumes are availible in TSM and I can move data to and from them although
an
audit library, a checkin or check out ends with the
mmsscsi.c(4318): Element address mismatch; slotInfo.elem = 7, slotInv.addr =
0
error.

In our production envioroment we have more differnt devices (DLT 2000, DLT
7000, HP DLT Libraries, IBM 3570-l06, l24, l36)
wich I can't get for  a test, so I'm a litte worried about what will happen
with this device if we migrate to TSM.

Has anyone seen this problems too and maby found a solution ?

TIA

Harald
harald.wassmann.hw AT bayer-ag DOT de
<Prev in Thread] Current Thread [Next in Thread>