|
You can contact me offlist. And I'll even put my boss in on it. He's the VP of IS. I can still remember the time we were having problems with one Domino server on NT. CEO asked how soon could we get it to the iSeries. Love this shop! We were a MSMail shop (and actually used a 400 for the file server). We migrated to Domino. We have numerous other ap's running on Domino other than mail. Our website http://www.dekko.com is Domino based. We even have a log in area for access to BPCS data - all Domino based programs. That app was so much quicker to rewrite in Domino than to webface, etc. When we did our migration to the 400 years ago IBM had me come up to Rochester and filmed my every step. They used it in some redbook or something. Stick this in your google search dekko site:ibm.com Routinely do hot swaps during the day. For example we have a Domino server called GDSSALES in a cluster with GDSSALES2 on another iSeries. Brought down GDSSALES and people seamlessly switched over to the other box. We do this sort of stuff at least every day. 24x7 access. It's amazing how we can get a new iSeries to Domino cluster but getting one to Mimix cluster all of the DB2 stuff is going to be a bear. Then again, Domino has this built in, db2, ON THE ISERIES, doesn't. (Google this: db2 udb stinger high availability) Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Burns, Bryan" <burnsbm@xxxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 08/19/2004 10:18 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Fax to Subject RE: Domino (was: IBM overhauls iSeries...) Do you mind if I contact you off-list? We too have Domino, (for an extranet app running on a Dell 1400sc with dual PIII processors), that we have talked about migrating to our iSeries when we upgrade our 820. Domino makes ODBC calls to the iSeries and we have had complaints about performance and are thinking maybe we can improve performance by having it on the same box. Also, boss is worried about having to do a restore on a windows machine if the Dell crashes. Although the Domino app is less than three years old, it is now a critical app for our business. We are also due for an Exchange upgrade and talked a little about using a Domino back end on the iSeries and keeping the Outlook client. We are in the dark as to how to justify moving anything to the iSeries so your suggestions would be most welcome. -----Original Message----- From: Ingvaldson, Scott [mailto:SIngvaldson@xxxxxxxxxxxx] Sent: Wednesday, August 18, 2004 7:28 AM To: 'midrange-l@xxxxxxxxxxxx' Subject: RE: Domino (was: IBM overhauls iSeries...) I guess that it depends on who you know. A former employer converted from MS Mail to Domino (on AS/400) in 1999. (5000 users, very happy with the results.) My current company uses Exchange for email, but has had a Domino server running a DB application for many years. We are currently migrating our Domino application to the iSeries and once done will evaluate moving email to Domino rather than upgrading Exchange. Regards, Scott Ingvaldson iSeries System Administrator GuideOne Insurance Group -----Original Message----- date: Tue, 17 Aug 2004 16:40:53 -0400 from: Pat Barber <mboceanside@xxxxxxxxxxxxxxxx> subject: Re: IBM overhauls iSeries for the long haul I have never seen Domino installed at any location other than IBM's. It pretty widely accepted that IBM took a major bath on the Lotus purchase. It's hard to make money on a product that given away for the most part.(pc world) michaelr_41@xxxxxxxxxxxxxx wrote: > Guess it's just different markets. Domino is a non-starter around > here...and I don't know anyone that uses Domino on iSeries. This message and accompanying documents are covered by the Electronic Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information intended for the specified individual(s) only. This information is confidential. If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, copying, or the taking of any action based on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- 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.