|
in order to ease my customers into "iSeries", i always used the term "iSeries AS/400", and for the truly uninformed... it was the long phrase "iSeries AS/400... it's like the difference between Win 95 and Win XP... this is the new & greatly improved version of AS/400 from IBM"! and now it will be (to me) "i5 AS/400, the new and greatly improved .... As IBM puts in their handbook, "the next generation..." i don't have a problem with this. i look forward to explaining the new features, and even the existing features not yet used by many companies. jim ----- Original Message ----- From: "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx> To: <midrange-l@xxxxxxxxxxxx> Sent: Wednesday, April 28, 2004 12:23 PM Subject: RE: i5....continues... > I was sort of under the impression that the name of the O/S was already > decoupled from the name of the hardware.... > > My 2¢, rebranding again after such a short time just dilutes the value of > the brand. Two years ago when I first tried to get my job description > changed to iSeries Administrator I was told "No one knows what that is." > The only reason it finally did get changed was that we bought an upgrade and > now the boss knows what an iSeries is. > > Regards, > > Scott Ingvaldson > iSeries System Administrator > GuideOne Insurance Group > > -----Original Message----- > date: Wed, 28 Apr 2004 10:11:14 -0400 > from: John Myers - MM <jmyersmm@xxxxxxxxxx> > subject: Re: i5....continues... > > With luck, they will FINALLY decouple the naming of the operating system > from the hardware that runs it!!! That is the greatest CURSE of we carry > in terms of "proprietary" positioning!!!! > > As long as the OS NAME is associated with the hardware, we will not be > perceived to be "open" by the computing profession!!! > > John > > 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. > >
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.