Don,

if you allow me I prefer Jack's order - Sun or even HP-UX before WinNT/2k
if any mentioning of SAN is made.
The way Win2k deals with SAN zoning, naming or any
addition/removal/reconfiguration in the fabric is just terrible. I had no
chance to experiment with XP or (God help me) .Net but to be honest do not
intend to try until forced to. Plug-n-Pray Windows functionality is
playing bad jokes in the most dangerous field of corporate data - the SAN.
Rule of thumb - avoid SAN-attached Windows machines (no matter TSM server,
TSM MgSysSAN or ordinary appl. servers) at any cost or at least separate
them in a fabric zone far from your responsibility. The rest is playing
with open fire.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Re: TSM Platform ?

Your order is pretty good, Jack;  based on what's been getting the
support,
I'd say AIX, Win2K, Solaris -- alot of focus is being placed on Win2K,
ref.
the LTO sales activity, MSCS support, etc...  and, for sure, don't add
platform learning curve to new product.  Also, multiple TSM servers can
coexist on any platform, but they pretty much require the same level (ie,
only once instance of the installed binaries),,, see the QuickStart book
for
the platform choice to see "clues" about doing it (it's somewhat
intuitive,
provided you know the given platform).

Don France
Technical Architect -- Tivoli Certified Consultant
San Jose, Ca
(408) 257-3037
mailto:don_france AT att DOT net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)