HP3000-L Archives

March 2006, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Charles Finley <[log in to unmask]>
Reply To:
Charles Finley <[log in to unmask]>
Date:
Wed, 1 Mar 2006 10:34:48 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (59 lines)
Is the use of Eloquence an HP3000-L list bias?  First, let me say that I am
NOT against the use of Eloquence.  We first used Eloquence in 1997 and I was
personnaly involved in persuading HP Germany into extending it so that it
would be a suitable substitute for TurboIMAGE.  The product and support was
excellent then and has improved. Nevertheless, when we actually seriously
get around to doing real work for a customer, the ones that engage us only
seem to want RDBMS's. We always ask the question "which database are you
targeting?". The answer to date has been either a specific RDBMS or a list
of potential RDBMS's. Just to be sure was ask " Are you considering
Eloquence?".  There are a lot of different ways people say no (usually its
"we want a standard product", but to date, they have all said no.

That said, any reader of this list might get the impression that the
question about migration can only be answered with "use Eloquence".  Why the
disconnect or am I reading too much into these few responses?  Is it a
demographic thing? Is this list more representative of the customer base or
less representative?

Moreover, database migration is only a only a part of a total migration
effort in our experience. These days, database tends to be a relative
non-event compared to the application testing, VPlus, JCL, command file, and
third-party tools migration effort.  Other things to consider are common
third-generation language (COBOL, FORTRAN, etc.) common 4GL (Powerhouse,
Speedware) and those pesky little languages like BRW, INFORM, etc.

Therefore, even if Eloquence provides the "best" database solution according
to someone's definition of what "best" is.  What does one do about all of
those other "application artifacts"?  Or is the original person who asked
the question interested in those things?

Charles Finley
619-795-0720

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Peter Osborne
Sent: Wednesday, March 01, 2006 10:03 AM
To: [log in to unmask]
Subject: Re: Migration recommendations; PRELIMINARY INQUIRY


We have (fairly) succesfully moved around 800 000 lines of Cobol to
Eloquence
on (Debian) Linux. This combo isn't usually considered for larger operations
as they like to be backed by large vendors.

Pete

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

__________ NOD32 1.1422 (20060301) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2