|
It is NOT about the name, but about PERCEPTION. If the world thinks AS/400is old, and you call it an AS/400, you are propagating OLD.
Perception is changed as soon as a new experience happens. As soon as
someone experiences something positive on the AS/400 (i.e. RPG CGI, RPG Web
Services, Java, Linux, virtualization, EGL, etc) they have a new perception
that the box can do more than they originally thought. I, for one, think
the name AS/400 still applies - AS=Application System right? (I am not sure
where the 400 came from). What's wrong with using that name for the boxes
that are currently leaving the production line? In the end, the whole
reason for all the new cool features coming out for System i is still so we
can use it to run applications.
I agree we need to keep up with IBM's naming no matter how bad it is, but we
also need to deal with reality. As others have more or less expressed, it
is not black and white but instead an education process to iterate it's
historic names and include mention of the new name. Just stating the new
name, when dealing with customers, is a dangerous game to play.
To wrap up my response, I still have no idea how to make a general reference
to the machine so I just say "i5" or "System i5". I have tried to follow
your posts of definition, but it seems that the context of the conversation
(hardware vs. software) dictates the name one should provide where as before
we could simply say AS/400 and everyone knew we meant the big black (or
white) box sitting in the corner running OS/400. Now we have to say System
i when talking hardware and i5/OS when talking about the software? What a
mess.
Trevor, I commend you for your efforts. You definitely are fighting an
uphill battle :-) I will try to do my best and teach those I am in touch
with.
Aaron Bartell
http://mowyourlawn.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.