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



Imagine going to a user group meeting and the thing you remember most is not to call it 400. Trevor must be earning his speaking fees.

On Sep 22, 2015, at 10:57 PM, PaultinNZ <paultormey@xxxxxxxxx> wrote:

Jim,

Could you share that " ... the memo for management to understand
how to explain our system
​"​ ?

I was just discussing this with a couple of colleagues yesterday and still
battle getting people to change.

Would appreciate that.

Thanks
Paul

On 23 September 2015 at 14:47, midrange <franz9000@xxxxxxxxx> wrote:

DB2/400 is ancient. So is DB2 for i5/OS and DB2 UDB (Universal Database)
for
iSeries

It is "DB2 for i " (at least for V7.1 and 7.2 - over 5 years)
although if I am ever talking to a non-Power i person, a trading partner, I
call it just "DB2".

Home page
http://www-03.ibm.com/systems/power/software/i/db2/

IBM has many DB2 products for various platforms

DB2 for Linux, Unix and Windows
DB2 on Cloud
DB2 for i <so what is wrong with this name?>
DB2 for z/OS
DB2 Server for VSE & VM
DB2 Spatial Extender for Linux, Unix and Windows
Spatial Support for DB2 for z/OS
DB2 BLU Acceleration

DB2 was originally IBM Database 2 in 1983 for MVS mainframe
We have thousands of customers accessing our system via a web interface (C#
and Win front end). No one calls it "AS/400" - management forbids it
(potential customers turn away or label us as "old" if we do). It is "Power
i " and the database is DB2.. I wrote the memo for management to understand
how to explain our system. Even 20 year employees get it... we replaced an
old floor model (a Power 5) with a rack system (Power 7+), called it "Power
i", and it's "new!".
Jim

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Glenn
Gundermann
Sent: Tuesday, September 22, 2015 7:19 PM
To: Midrange Systems Technical Discussion
Subject: Re: Is DB2/400 still the correct terminology fo DB2 on the IBM i?

Same here.

-----Original Message-----
From: Jerry Draper <midrangel@xxxxxxxxxxxxx>
Sender: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>Date: Tue, 22 Sep
2015
15:12:29
To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>
Reply-To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Is DB2/400 still the correct terminology fo DB2 on the IBM i?

We just call it an IBM I and refer to the database as db2.

Jerry



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


--
Paul Tormey
3/11 Bramley Drive
Farm Cove
Auckland
2012
New Zealand
Home: 09 576 3415 or 0064 9 576 3415
Mobile: 021 810615 or 0064 21810615
--
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 ...

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.