I am having some problems in defining a shared library clients drives.

Here is what I have:
  Two servers running TSM 5.1.1.2 on Solaris 8, with a IBM 3584 library
-w- 8 drives.
  Both servers see all the drives and control ports (/dev/rmt/*mt and
*smc), I can define non shared libraries and drives to each server
individually, so there is nothing wrong with the SAN or zoning.

I believe I have followed all the correct steps to properly define the
library to the library manager server.

On library manager:

tsm: ADSMA> q library SANLIB f=d
                  Library Name: SANLIB
                  Library Type: SCSI
                        ACS Id:
              Private Category:
              Scratch Category:
              External Manager:
                        Shared: Yes
                       LanFree:
            ObeyMountRetention:
       Primary Library Manager:
                           WWN:
                 Serial Number:
Last Update by (administrator): ME
         Last Update Date/Time: 10/10/02 16:08:48

tsm: ADSMA> q drive f=d
        (reports all 8 drives)

On library client: q library SANLIB f=d

                  Library Name: SANLIB
                  Library Type: SHARED
                        ACS Id:
              Private Category:
              Scratch Category:
              External Manager:
                        Shared: No
                       LanFree:
            ObeyMountRetention:
       Primary Library Manager: ADSMA
                           WWN:
                 Serial Number:
Last Update by (administrator): ME
         Last Update Date/Time: 10/10/02 17:12:10

tsm: ADSMB> q drive f=d
        (reports no drives after defining the SANLIB to the library
client)

The manual says that you have to define the drives to the library client,
and then define the paths.
BUT:

tsm: ADSMB> define drive SANLIB DRIVE1
ANR8403E DEFINE DRIVE: Operation not allowed for SHARED libraries.
ANS8001I Return code 3.

I talked to LVL 1 support, and they pointed to somthing that said the
documentation was wrong and that those drives will be automatically
defined when the shared library client initializes (it initializes with no
errors reported on the library manger or library client)  But the drives
are not being automatically defined.  A network snoop between the two
servers upon initializing shows text passing from the library manager to
client containg the drive names, so something is happening, but not
completely working.

I am still waiting for LVL 2 to respond.

Does anyone have any ideas?

Matthew Glanville
matthew.glanville AT kodak DOT com
Eastman Kodak