Larry,

Close but not exactly the levels you are asking about. We were running
with a 5.2.2.5 master and two other servers (another 5.2.2.5 and a
5.1.5.4) sharing without problems.

We are now at 5.3.1.0 on the master and have a 5.3.1.0 and the old
5.1.5.4 machine sharing.... We are working on shutting down the 5.1.5.4
box but still waiting on some old backup data to expire off.

The combination worked fine for us.

Curt Magura
Lockheed Martin EIS
Orlando Fla.
321-235-1203


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Mcnutt, Larry E.
Sent: Wednesday, May 11, 2005 11:46 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM 5.2.3 and library compatability.

Hello TSMrs,

We are running two AIX TSM servers at 5.1.7.0. - tsm1 and tsm2. They
share a
3494 library, and tsm1 is the library master.  We plan to upgrade tsm1
initially to 5.2.3.0, and in a few weeks upgrade tsm2.  This seems to be
a
valid combination with the library master at 5.2.3 and the library
client at
5.1.7 according to the readme file.  We are not able to test this prior
to
actually doing the upgrade, so it would be comforting to hear if anyone
has
actually had a similar situation.

>From the readme-----
************************************************************************
****
****
* $$2 Added library sharing compatibility
*
************************************************************************
****
****

Version 5.2.2 Servers acting as a library manager are now backwards
compatible
with version 5.1 and 4.2 servers acting as a library client.  Version
5.2.2
servers acting as library clients remain incompatible with version 5.1
and
4.2
servers acting as library managers. When upgrading multiple servers
participating in library sharing to version 5.2, the servers acting as
library
managers must be upgraded first to maintain compatibility among the
servers.

Thanks,
Larry McNutt
The Timken Company

-----------------------------------------
This message and any attachments are intended for the individual or
entity
named above. If you are not the intended recipient, please do not
forward,
copy, print, use or disclose this communication to others; also please
notify the sender by replying to this message, and then delete it from
your
system.    The Timken Company / The Timken Corporation