× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Thu, Feb 5, 2009 at 15:06, <rob@xxxxxxxxx> wrote:
So, what do you expect a person who buys the same hardware as you but runs
only AIX on it to call it? An AS/400?

Aah, the joys of marketing.

The problem here is that almost nobody refers to their Windows servers
as "IBM System x". Instead it's more along the line of "We run our
Windows on IBM servers and IBM blades". Nobody really cares if they
are called System x or xSeries.

IBM rebranded the AS/400 hardware (bear with me here, there may be a
more correct way of saying this, but this is easier) as iSeries - but
the hardware is secondary to the software - OS/400 and AS/400 was a
nice combo, and many people are more aware of the name AS/400 than
OS/400 (it would be interesting to know why, but i sure don't know).

The OS was rebranded later, in one of the more stupid moves by IBM to
i5/OS - V5R3 wasn't rebranded, V5R4 was partially rebranded and when
V6R1 came out it had yet another name.

So we're stuck here with System i Access V6R1 to access our IBM i
running on IBM POWER, which is installed into a folder called Client
Access.

I wonder how the next name of the Access software will be.

IBM i on IBM POWER Access V6R2

IBM would do themselves a lot of good if they just stuck the system
name in a branding.xml on IBM.com somewhere, signed it digitally, and
have all their software retrieve that file daily. Or hourly.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.