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



Jerry,

In a one-server shop, users calling a server by any name was something we
did, because we had this one amazing thing doing all the work. In a modern
environment, where applications are integrated, and you cannot tell where
they are running, what is the point of using the name of the server?

Trevor


On 9/29/11 3:30 PM, "Jerry C. Adams" <midrange@xxxxxxxx> wrote:

I disagree with those who state that it doesn't matter what the users call
the system. At my previous job we had a Model 520 (Power 5) that I
referred
to over the intercom and in conversation as a "System i". A few users
asked
me, Why? It's still an AS/400. Gave me the opportunity to explain that
this ain't your father's AS/400 and go over some of the differences. It
made an impression because, if friends of theirs said something about us
being on a legacy machine, they proudly said, No, we use the modern System
i. The president/owner was the hardest to convert, but then he started
bringing in friends, etc., and giving them a tour of his modern data
center.

I agree that the application software makes a world of difference in the
perception. Here and at the previous job the base application is S/36
(RPG
II, OCL). People get used to it and think this defines the system's
capabilities. Simple things like a subfile (still green screen, of
course)
blow 'em away - and then they start salivating. Another simple example:
last month some auditors wanted some data in a spreadsheet. My boss told
them it couldn't be done but we could send them a report. I pointed out
(in
a politic manner) that we could do the spreadsheet thing (though we
couldn't
have before I externally defined the database). He was impressed; more
with
the system, I think, then with me not knowing what I did to get us to that
point. Sigh. But that's the advantage to working in the 36EE - anything,
absolutely anything, I do looks futuristic!

Jerry C. Adams
IBM i Programmer/Analyst
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


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

Scott,

Glad to hear that Scott. I agree, what wording are you putting on yours, I
will put the same wording on mine.

And challenge everyone else to do the same.

And if you think it won't make a difference I say - Fine, but it won't
hurt
anything to do it either, so what is your real reason?
You prefer to just argue and do nothing??


John


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, September 29, 2011 1:40 PM
To: Midrange Systems Technical Discussion
Subject: Re: renamed to: Get users to stop saying AS/400

hi John,

I think this is a great idea.

Indeed, back in 2002 when we bought an iSeries (we previously had an
AS/400) I did this -- I put iSeries on the sign-on screen, so everyone
would
see it every day. I thought it was a great idea.

But, it didn't work. They still called it AS/400.

Still, it's a good idea, and I think I'll do it again.


On 9/29/2011 10:10 AM, John Allen wrote:
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.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.