Now that I have all of my element address problems squared away I have run into
another issue.
04/01/04 11:36:41 ANR8422I CHECKIN LIBVOLUME: Operation for library AUTOLIB
started as process 39.
04/01/04 11:36:43 ANR9999D mmsscsi.c(7648): ThreadId<38> Element address
mismatch; slotInfo.elem = 0, slotInv.addr = 4137
04/01/04 11:36:43 ANR8832E CHECKIN LIBVOLUME for volumes in search mode in
library AUTOLIB failed.
04/01/04 11:36:43 ANR0985I Process 39 for CHECKIN LIBVOLUME running in the
BACKGROUND completed with completion state FAILURE at
more... (<ENTER> to continue, 'C' to cancel)
After looking up the ANR problem code I have found IBM's site states
Problem
After adding new drives to an existing library the following errors are being received
on the TSM Server.
ANR9999D mmsscsi.c(7635): ThreadId<54> Element address mismatch; slotInfo.elem = 0,
slotInv.addr = 1212
ANR9999D mmsscsi.c(7635): ThreadId<54> Element address mismatch; slotInfo.elem = 0,
slotInv.addr = 1212
Cause
The addition of drives to a library often entails the loss of some storage slots. This
will cause a discrepancy between the information that the TSM server has stored for
the library and what the library now returns from an inquiry.
Solution
Delete the drive and library paths and definitions in TSM. Then redefine the library
and drive definitions and the paths for the library and drives. After doing so, run
the two following check in commands to repopulate your TSM library inventory:
checkin libvol <library name> search=yes status=scratch checkl=bar
checkin libvol <library name> search=yes status=private checkl=bar
***NOTE: The above two commands assume that you have a barcode reader in your library.
If you do not, use "checkl=yes".
I have tried this solution several times but still have the same ANR issue.
anyone have any suggestions?
R.
