RE: renamed to: Get users to stop saying AS/400

But if the users think they are working on a '400' they talk about a '400'.
The users need to talk about IBM Power or IBM i.
I know my users don't need to be sold on the system, but they do need to
know what the system is.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Trevor Perry
Sent: Thursday, September 29, 2011 11:39 AM
To: Midrange Systems Technical Discussion
Subject: Re: renamed to: Get users to stop saying AS/400

Paul,

The need to promote IBM i to the users is not required. It is the IMAGE of
the platform to the industry, to the community, to business, to managementŠ

Trevor

On 9/29/11 11:39 AM, "paul therrien" <paultherrien@xxxxxxxxxxxxxxxxxx>
wrote:

+1
This is beautifully simple.
Thinking about this I realize that this is what is called 'branding'
and this is what all these emails have been about.
I think this is very important and would be an initiative that IBM
ought to implement.
This is also what the LinkedIn midrange group ought to be promoting.
They
have an on-going thread of 'What would you do to promote the IBM i?'
(Or something along those lines.) And this is a very good answer to
that question.
I will post your idea over there as well, if you don't mind.
....
Beautiful, simple.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Allen
Sent: Thursday, September 29, 2011 10:10 AM
To: 'Midrange Systems Technical Discussion'
Subject: renamed to: Get users to stop saying AS/400

Your comment about users seeing MacBook Pro or Windows 7 constantly
brings up an idea I never thought of.

How about everyone changing their companies Sign On screen (you can
change the sign on screen) And put:
Welcome to IBM i
Or
Welcome to IBM i running on Power System Or Some other term everyone
can agree on Some color everyone can agree on Location everyone can
agree on Just make it consistent for EVERYONE

Users will see it every day or multiple times a day.
They will eventually start calling it by something other than AS00

John


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Loyd Goodbar
Sent: Thursday, September 29, 2011 10:37 AM
To: Midrange Systems Technical Discussion
Subject: Re: Classes for IBMi/iSeries?

+1 to this. I don't call my MacBook Pro a PowerBook because right under
+the
screen, it says "MacBook Pro". The name is clearly visible to me. Every
time I turn on my work computer, I see Windows 7, not XP or 2000 or a
black DOS screen. Now, if my only interaction running IBM i
applications is via 5250 or the web, there is little or no indication
whether I'm running on an AS/400, iSeries, or Power. It's all about the
visibility. The users call it "AS/400" becuase they've used the same
software packages for 18+ years with no visible indication of the
platform change from AS/400 to iSeries to System i to Power. And in the
end, isn't that how it should be?

Loyd

On Thu, Sep 29, 2011 at 9:20 AM, Charles Wilt
<charles.wilt@xxxxxxxxx>wrote:

Correct me if I'm wrong...

But my understanding, and I've never used a S/36 or S/38), is that
from a green screen user's perspective, there's obvious differences
between S/36, S/38 and AS/400....

Now compare that to the difference's between AS/400, iSeries, System
i, POWER running IBM i...

It's no wonder the users still call it AS/400!

Charles

On Thu, Sep 29, 2011 at 10:09 AM, Trevor Perry <trevor@xxxxxxxxxx>
wrote:

Jerry,

It was not quite clear.

Did you call the AS/400 a S/36, because it could run S/36

applications?

Did you call the AS/400 a S/38, because it could run S/38

applications?

If the answer is yes, then calling IBM i an AS/400 is the same thing.
If no, then...
Do you call IBM i an AS/400 because it can run AS/400 applications?

--
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.

--
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.

--
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.