Bad... total cost of ownership is too high.  Too many fingers in the pie (tape 
group, dasd group, TCPIP group, operations etc...  When you begin to figure out 
total cost of ownership, you have to add
all of these support teams into the equation, not to mention the internal 
charge (funny money) for MIPS usage on the mainframe that you'll incur. TSM 
will also be at the mercy of the mainframe IPL
schedule as well, which typically is on Saturday night into Sunday morning (a 
window that you really want open for your large archives or db backups)

If you're on any other platform, your costs should drop significantly.  e.g.  
If you have a P690, you have 1 SA managing that server.  You don't need nearly 
the staff that you'd require for a
mainframe solution.  How often does an AIX or Sun machine have to be taken down 
for maintenance? (not often).  And finally, a P690's I/O is comparable to a 
mainframes.

If you get the budget, go with a big Unix system.  Run screaming from the 
mainframe solution.  You'll save a lot of headaches and meetings.  Just my 
opinion.

Regards, Joe
-----Original Message-----
From: Spearman, Wayne [mailto:wmspearman AT NOVANTHEALTH DOT ORG]
Sent: Thursday, April 03, 2003 1:05 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM on Mainframe


We do. It works fine for us, but we are migrating off to Unix for D.R.
reasons.

-----Original Message-----
From: LeBlanc, Patricia [mailto:Patricia.Leblanc AT LIBERTYMUTUAL DOT COM]
Sent: Thursday, April 03, 2003 1:02 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TSM on Mainframe


Does anyone out there use TSM on a mainframe?

Good?  Bad?  Indifferent??

Thanks!!

pattie


This message and any included attachments are from NOVANT HEALTH INC.
and are intended only for the addressee(s). The information contained
herein may include trade secrets or privileged or otherwise confidential
information. Unauthorized review, forwarding, printing, copying,
distributing, or using such information is strictly prohibited
and may be unlawful. If you received this message in error, or have
reason to believe you are not authorized to receive it, please promptly
delete this message and notify the sender by e-mail.

Thank you.