Re: solaris tsm server

Gerald,
device file /dev/rmt/0mt is for drive, not for library. You should have in
your /dev/rmt directory something like xlb, where x is number which depend
on the order, in which you run add_drv commands for drives and library. It
does not matter what this number is, but you have to have this file in
your
/dev/rmt directory and use it in def libr command. Sample content of my
directory /dev/rmt is:

lrwxrwxrwx   1 root     other         45 Feb 22 15:03 0lb ->
../../devices/pci@1f,0/pci@1/scsi@3/lb@0,0:lb
lrwxrwxrwx   1 root     other         46 Feb 22 15:03 0lbt ->
../../devices/pci@1f,0/pci@1/scsi@3/lb@0,0:lbt
lrwxrwxrwx   1 root     other         45 Feb 22 15:03 1mt ->
../../devices/pci@1f,0/pci@1/scsi@3/mt@5,0:mt
lrwxrwxrwx   1 root     other         46 Feb 22 15:03 1mtn ->
../../devices/pci@1f,0/pci@1/scsi@3/mt@5,0:mtn
lrwxrwxrwx   1 root     other         46 Feb 22 15:03 1mtt ->
../../devices/pci@1f,0/pci@1/scsi@3/mt@5,0:mtt
lrwxrwxrwx   1 root     other         45 Feb 22 15:03 2mt ->
../../devices/pci@1f,0/pci@1/scsi@3/mt@6,0:mt
lrwxrwxrwx   1 root     other         46 Feb 22 15:03 2mtn ->
../../devices/pci@1f,0/pci@1/scsi@3/mt@6,0:mtn
lrwxrwxrwx   1 root     other         46 Feb 22 15:03 2mtt ->
../../devices/pci@1f,0/pci@1/scsi@3/mt@6,0:mtt


Ing. Jozef Zatko
Login a.s.
Dlha 2, Stupava
tel.: (421) (2) 60252618



I'm not all that familiar with running TSM on solaris.. trying to
configure
an ATL tape library on a test box I have here. When I define the library
it
crashes the TSM server:

05/14/02 17:58:01      ANR2017I Administrator ADMIN issued command: DEFINE
LIBR
                        lib_tape_1 libt=scsi devi=/dev/rmt/0mt

05/14/02 18:09:14      ANR9999D mmstxn.c(219): ThreadId<42> Lock
acquisition

                        (sLock) failed for MMS universe lock.

05/14/02 18:09:14      ANR2033E QUERY LIBRARY: Command failed - lock
conflict.
05/14/02 18:09:14      ANR9999D mmstxn.c(219): ThreadId<40> Lock
acquisition

                        (sLock) failed for MMS universe lock.

05/14/02 18:09:14      ANR2033E QUERY LIBRARY: Command failed - lock
conflict.

05/14/2002 18:12:57  ANR7824S Server operation terminated.
05/14/2002 18:12:57  ANR7823S Internal error LOCKCYCLE02 detected.
05/14/2002 18:12:57  ANR9999D Trace-back of called functions:
05/14/2002 18:12:57  ANR9999D   0x00000001000837CC  pkAbort
05/14/2002 18:12:57  ANR9999D   0x0000000100083858  pkLogicAbort
05/14/2002 18:12:57  ANR9999D   0x00000001009865EC  CheckLockCycles
05/14/2002 18:12:57  ANR9999D   0x0000000100982080  TmFindDeadlock
05/14/2002 18:12:57  ANR9999D   0x0000000100981D60  TmDeadlockDetector
05/14/2002 18:12:57  ANR9999D   0x0000000100087818  StartThread
05/14/2002 18:12:57  ANR9999D   0xFFFFFFFF7EC1F844  *UNKNOWN*
05/14/2002 18:12:57  ANR9999D   0x0000000100087710  StartThread

my question is whats going on here? It's possible I suppose I might have
the
device wrong.. It's fairly likely I don't have the ATL library device
driver
loaded as well. How would I check this on solaris? How do I determine what
device the library and it's drives are? I'm guessing that's probably my
problem here (a lack of solaris knowledge). Appreciate any feedback.



Regards,

Gerald Wichmann
Senior Systems Development Engineer
Zantaz, Inc.
925.598.3099 (w)