HP3000-L Archives

November 2001, Week 2

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:
John Saylor <[log in to unmask]>
Reply To:
John Saylor <[log in to unmask]>
Date:
Tue, 13 Nov 2001 08:09:23 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (125 lines)
Several middleware tools exist as Adam points out NetBase-Client is a great
tool for companies that like to build there own interfaces

But building a coexistence between the HP3000 and other platforms. Here is
the answer.....

BridgeWare(tm) - - Continuous Synchronization/One time data migration from
HP 3000 to Oracle or SQL Server Databases/Open Systems

Ensuring data consistency across your LAN or WAN is a difficult process.
This involves moving data between MPE and emerging systems. To automate the
task, Quest Software offers BridgeWare(tm) for MPE:


Automatically creates target file structures in Oracle or SQL Server
databases
Passes real-time or scheduled delta changes - extractions to a
transformation engine that executes data manipulation, cleansing or
transformation on data in-flight as the data moves to heterogeneous file
structures or RDBMS in the open systems environment
Automatically resolves data differences between MPE and Oracle
Automatically generates scripts through a GUI interface for initial loads
and incremental loads. These core transcripts can be executed for clone
movement or customized to add more complex transformations, manipulations,or
data cleansing that may be required.
BridgeWare, the cooperative endeavor of Quest Software and Taurus Software,
enables data movement between HP 3000 and open systems. BridgeWare addresses
one-time data migration; continual data movement to data warehouses, data
marts or new open system applications; and consolidates data into a
centralized common database, data warehouse, data marts or new application
data structures.
BridgeWare provides real-time or scheduled posting of TurboIMAGE, KSAM, or
updates to MPE files to an Oracle, Informix, SQL or DB2 RDBMS running on
UNIX or NT systems, giving users the power to access and update data across
multiple platforms with the most popular industry databases on the market.

For more information you an view our website at:

http://www.quest.com/middleware/pdfs/MdlWare.pdf

or

Schedule a brief BridgeWare chalk-talk that can go more in-depth to your
particular interests. Additionally there is a BridgeWare presentation online
you may wish to view. Select the "Product Presentation" in the margin to
download the presentation if you wish.

Please contact us and request to speak to a salesperson in your area.


Quest Software
Nasdaq:QSFT
8001 Irvine Center Drive
Irvine, Ca. 92618
www.quest.com

949.754.8999 Fax
800.306.9329 Toll-Free





-----Original Message-----
From: Adam Dorritie [mailto:[log in to unmask]]
Sent: Tuesday, November 13, 2001 7:13 AM
To: [log in to unmask]
Subject: Re: ODBCSE drivers have high latency on HP3000


Not to jump into the middle of a religious war over data access middleware,
but I believe that David's message isn't quite true (depending, of course,
on how you parse the word "native").  There are at least two products that I
know of that provide a direct interface to IMAGE without the use of ODBC
(and I wouldn't be surprised to find even more vendor offerings).

<pseudo plug (offered only to demonstrate other non-ODBC alternatives)>

Quest Software offers their Netbase Client software which is a set of APIs
which mirror IMAGE, KSAM, MPE File intrinsics and some OMNIDEX calls.  Use
them just like you use the MPE calls on Windows and some Unices.

Minisoft, in addition to an ODBC driver, offers a product called Middleman
which provides IMAGE-style (and KSAM-style and MPE File-style) API calls.
Windows-only, I believe, but I am open to correction.

</pseudo plug>

While ODBC may offer a decrease in performance in some (or even most) cases
(I haven't done the benchmarking), it also offers the ability to be
immediately used with hundreds of programs that support the standard with
minor accommodation for the SQLization of IMAGE v. other RDBMS drivers.  Any
API interface will require explicit coding.

I won't argue about whether or not one should use ODBC or a proprietary
interface-- they're different tools that meet different sets of
needs/desires.  I would never use a claw hammer to break concrete, but woe
be to he who uses a jackhammer to pound in a nail to hang his
mother-in-law's picture over the fireplace.

Regards,

Adam Dorritie
Easy Does It Technologies LLC
(702)270-6402
http://www.editcorp.com

David Thatcher writes:

> <plug>
>
> Our ADBC product is the ONLY native interface to IMAGE/SQL.  ODBC is
> proprietary inefficient method of accessing IMAGE databases.   You can
> access IMAGE from ANY platform (Mac, Unix, Linux, MPE, PC...)
>
> http://www.advnetsys.com
>
> </plug>

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

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

ATOM RSS1 RSS2