|
I really am stepping out of my comfort (knowledge) zone here, but I have to ask. Doesn't the scalability of the AS/400 (including model changes and LPAR) make it a good choice for your reason #1? Doesn't the reliability of the AS/400 (and the options for mirroring, etc. and hot-swapping) negate the problems of #2? Doesn't the AS/400 have memory pools and tuning capabilities to handle the performance issues you raised in #3? As for #4: God help us all. (I have never backed down from NT bigots who slam the AS/400. I just state the obvious facts; never goes down, doesn't require gurus just to keep it running, no BSODs / GPFs that require reboots/re-IPLs, rock-solid built-in security, the list goes on and on and on... But I digress.) I will just say that in my experience as a contractor in various shops, I've never seen Novell go down, and I've been in shops where NT is cursed like the antichrist, but in others it performs like a champ (like this shop). Please educate me. - Dan Bale -----Original Message----- From: Schenck, Don [mailto:Don.Schenck@WL.com] Sent: Wednesday, March 15, 2000 9:34 PM To: 'MIDRANGE-L@midrange.com' Subject: RE: as400 as exchange server 1. As technology gets faster and cheaper, you can implement faster servers just like that (snapping his fingers). 2. Avoid Single Point Of Failure. This can be a biggee. We can use COM+ to put our business objects on multiple servers. This gives load balancing and avoids the dreaded Single Point Of Failure. 3. Performance can be spread or isolated. That is, a Departmental Server can be used for performing queries. When Jodi in Accounting executes the "Query From Hell" where she joins the 13 million transaction records to the 35,000 vendor table, the Exchange Server and the MTS Server keep humming along, oblivious to Jodi's actions. 4. It's fun and geeky. Running Big Brother on a workstation to "watch the network" is cool. That sounds like a crock, but did you ever think HOW MANY "business decisions" are made because something's "cool" or impresses the guy in the next seat on the flight to Chicago. Number four sucks, but poop happens. Peace, -- Don Schenck -----Original Message----- From: boothm@earth.Goddard.edu [mailto:boothm@earth.Goddard.edu] Sent: March 15, 2000 8:02 PM To: MIDRANGE-L@midrange.com Subject: RE: as400 as exchange server While I agree that NT bashing does get old, and that NT has a lot going for it (Hey, Windows 2000 has been out a month and sold 7 1/2 million copies already), I am curious about the paradigm. They have 20 NT servers? 20?!? That is a big number. Why so many? I ask that because I see NT servers litter server farm racks like baggage on an airlines baggage cart. But then see one or maybe two AS/400 machines off to one side doing the work of the organization. What is it that all of those servers are doing? Why do they need all the boxes? What is the feature they are getting by having 20 boxes? _______________________ Booth Martin boothm@earth.goddard.edu http://www.spy.net/~booth _______________________ "Schenck, Don" <Don.Schenck@WL.com> Sent by: owner-midrange-l@midrange.com 03/15/2000 03:02 PM Please respond to MIDRANGE-L To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com> cc: Subject: RE: as400 as exchange server Ya know, this WinNT bashing gets really old and NOT realistic. WHY is it that my client has 20 ... COUNT 'EM TWENTY ... NT boxes and during the past 30 months that I have been here they have not had one, NOT ONE, crash. Perhaps they know what they're doing??? -----Original Message----- From: L. S. Russell [mailto:leslier@datrek.com] Sent: March 15, 2000 1:13 PM To: MIDRANGE-L@midrange.com Subject: Re: as400 as exchange server > Switch from MS exchange to the AS/400! You'd have to be crazy! Never > mind all the Microsoft bashing, exchange is great and if you put it a > standalone server and just leave it, it will keep running and running > and..... Exchange server will only run until Win*** crashes and the same goes for any product for Win***, when the OS is up your server software is up and that is that. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.