|
Hope that made sense. ;-) Vern
not sure what you mean with the 810 now and an i5 a year form now. ----- Original Message ----- From: "Vern Hamberg" <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Tuesday, May 18, 2004 10:30 AM Subject: Re: I5 vs. 810
> All the other repsonses are valid - there are good things and some price > advantages in the i5, it seems. > > But against that is the hassle of a new release. There are always problems. > Some would say wait until at least the first CUME before getting a new > release. You need to weigh costs and benefits, and with a new release, > there is likely to be a cost for it getting really shaped up. Put your > actuaries on it. ;-) > > Of course, there's also the extra cost of a 2-stage purchase in a short > time - 810 now, 520 within a year, say. > > HTH > Vern > > At 08:23 AM 5/18/2004, you wrote: > >We had just finished up our quotes for a new 810 when the i5 was announced. > >I and my compatriot in arms have recommended to the IT Director to not worry > >about the i5 and just go with the 810. > > > >We're an insurance company with two computer people running the whole > >company. When we get our new machine, we are basically hooking it up, > >transferring data and going live. We aren't able to beat it up for a couple > >months to test it first. This is mainly why I say going with the 810 and > >5r2 is the better route, because there are less surprises and our vendor has > >been using this line for their application for years. > > > >He (Director) still wants to know the "industry's" opinion on whether we > >should go i5 or 810 and whether going to 5r3 is risky or not. > > > >Do you have any feedback and/or any links for articles about this? > > > >This is one I have found so far. > >http://www.midrangeserver.com/fhg/fhg051204-story05.html > > > >Adam Lang > >Systems Engineer > >Rutgers Casualty Insurance Company > >http://www.rutgersinsurance.com > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l.
_______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.