David,
Do you have any feel for any performance impacts(if any) we'd pay going to
a 'remote' database environment. Granted, same box, hipersockets, etc,
but it is remote non-the-less.
>Your biggest obstacles to substituting UDB on Linux for DB/2 on z/OS will
>be:
> a) figuring out how to buy it
We did get pricing through Mainline.
> b) working within the technical restrictions
I'm more curious on this item, and I believe it is on database
sizes,
but I'm not educated enough yet on this.
> c) overcoming your IBM rep's reluctance to losing z/OS MIPS and
>corresponding revenue.
We would actually stay stable, vs reduce, most likely not growing. We are
not
big, infact we deal very little with IBM directly anymore. Our entire
traditional mainframe environment is only 600Gb for everything, DB2
probably
a third of that. So we are not huge.
> You should also price HA
> software for L/390 and network HA hardware as part of the mix as well.
In our cost case we did include the cost of Linux support, training(for
Linux, DB2, and VM), but what HA items are you talking about? We have a
standby 9672-R26 that would be capable of running VM, and linux in a
pinch,
it is our D/R box. I'm thinking shared DASD, and if the server is not
available in its' normal home, we can boot on the 9672-R26. We were not
thinking of continuous availablility, as it may be overkill for us, but I
would be curious what you are thinking.
The FUD from the DBA's is that they've 'heard' that DB2 on linux on the
mainframe will be a dog.
Your idea's of selling them on their importance is a good one, and I guess
would have
thought it would have been obvious. I'll have to work on that.
Dave
__________________________________________________________
Dave Jousma
Lead Systems Administrator - Information Technology
Spartan Stores, Inc.
PO Box 8700
Grand Rapids, MI 49518
(616) 878-2883
Email: [EMAIL PROTECTED]
