I'm not sure if I've missed a previous post, but has anyone posted an
example (or URL to one) source and setup of ADBC use in Java on the HP3000
from within Apache?

A working example that actually gets info from a form, queries a database,
and returns a table of results would be a great kick-start for the CGI
challenged.....

Come to think of it, so would a simple example of PERL doing the same thing
- IIRC Perl can call the Image Intrinsics and format the returned data.

I know this is a bit cheeky, and I don't expect those developing commercial
applications to reveal secret methodologies, but maybe the Java team, the
Apache team and the Perl team can post these.

Of course, they probably have, and I've just missed the posts- if so, sorry,
slap my wrists, and I'll be quiet.

As an aside, we use sockets to get Health Care data from the HP3000's to MS
IIS .asp pages. Back in 1995, we played a lot with ODBC, but found that our
data structures just didn't make it easy to present data the way we wanted
to - the compromise was just too great - and we already had reusable
"Objects" on the HP3000's that were pretty easy to call from a Cobol socket
server.


Regards

Neil



-----Original Message-----
From: David Thatcher [mailto:[log in to unmask]]
Sent: 24 May 2000 09:11
To: [log in to unmask]
Subject: Re: Accessing Image: ODBC vs Sockets


> At 12:24 PM 5/23/00, Dovid Samber wrote:
> >    We are planning a web page for customers to access order status
> >information and have become aware of the high resource consumption on the
> >3000 when accessing Image data via ODBC.  An alternative of using Sockets
> >and staying native mode on the 3000 has been proposed.
> >    Any negatives in going the Sockets route?
>
> Caution, this reply contains <PLUG>s.
>
> Neal Kazami Wrote:
> ODBC calls CAN use a lot of CPU/Disc IO on the HP3000. With careful limits
> placed on the SQL statements used in your web application, resource
> consumption can be kept very small.
>

<plug>

What's great about ADBC is that you do not have to be careful... ADBC is
easy to use , SAFE and you take advantage of the powers of IMAGE through its
native intrinsics using Java. NO SQL, NO ODBC and NO JDBC. ADBC offers
native intrinsics access to IMAGE, KSAM, MPE and SPOOL files from ANY Java
platform that implements Java(PC, Mac, Unix, Linux, Handheld MS CE
Devices...).

ADBC version 2.1.0 supports subroutines, functions and system intrinsic
calls from any Java platform that implements Java.  No need to replicate
business logic, ADBC allows you to reuse existing business logic on your HP
e3000.  Just use our intrinsic class to wrap any pre-existing subroutine
from any XL on your HP e3000, from any remote platform.

ADBC Out-performs ANY ODBC and JDBC solution. just ask our customers...

Regards,
David Thatcher
Advanced Network Systems, Inc.

(908) 231-5342

</plug>