To all,

I've a bit of a challenge.

We're running TSM 5.1.6.3 on two AIX systems sharing a 3584 Tape library system.
One AIX server acts as library manager with the library definitions and paths 
and drives.
The AIX server acting as client only has the 'shared library' definition and 
one tape path relating it to the Library manager.
So far no problems all seems to work fine.
Now I want to add another TSM server to this running on AIX, same level also 
4.3.3, but running TSM 4.2.1.15.

So this is what I did:
On library manager      - defined the TSM server running 4.2.1.15
                        - defined tape path(s) to new server, only those 
'known' to the new client due to the zoning of the switch to which the client 
is connected

On library client               - defined shared library
                        - defined shared drives
                        - defined new device class for the new to use library

Here comes the real problem; when I start a process on the client which 
requests a tape, the client starts a session with the Library manager and the 
manager starts the mount of a scratch tapes and then informs the client via 
another session about which volume is mounted and on what drive.
Then until now I've got a 100 % score on mismatching, for the manager loads the 
tapes on drives NOT known by the client, what is exactly what the client shows 
in the actlog and the process gets cancelled.

What I don't understand is WHY does the manager NOT load the scratch tape on a 
drive related to the tape paths defined for this client, it just seems to pick 
any available drive and informs the client.
What's the use then of defining the paths if they're not taken into account 
during the mount?


Marcel Anthonijsz
Central Data Storage Manager (a.k.a. storman)
Shell Information Technology International B.V.
PO Box 1027, 2260 BA  Leidschendam, The Netherlands

Tel: +31-70 303 4984
Mob: +31-6 24 23 6522