HP3000-L Archives

November 1998, 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:
"Vaala, Evan" <[log in to unmask]>
Reply To:
Vaala, Evan
Date:
Mon, 9 Nov 1998 15:40:19 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (62 lines)
Just wanted to add that I have been expirementing with the ADBC technology.

I have been primarily interested in the transaction capabilities of ADBC.  I
like/trust the ability to lock a database/dataset/KSAM/MPE File and perform
a put/update/delete against it and then unlock.

ADBC gives you an object oriented aproach to perform native Turbo Image and
Mpe FXXXXX calls.  You can select the desired locking mode( Conditional /
Unconditional ) on databases or datasets.  I feel much more in control of my
transactions.

Having studied many of the Java API's, it appears that ADBC is a cross
between Native Turbo Image calls and JDBC 2.0.  ADBC has the
"setFetchSize()" method which is in the new JDBC 2.0  spec.  This allows the
fetch size to be set high for reports/read only information, or to set it
low, or even down to one for transactions.  The fetch size is the number of
records pulled from server to client in a single request - thus enhancing
I/O performance with larger fetch sizes.  It also includes alot of the
cursoring methods of JDBC 2.0

Writing to spooled devices is nice to have the ability to add a new client
front end to an app, but still print to pre-printed PO forms, or checks,
etc...  Paperless is our ultimate goal, but it's nice to have this option to
help step to that point.

I have also expiremented with reading a series of spool files in from an
HP3000 and writing them straight to individual entries in a single zip file
using ADBC and the java.util.zip package.  The zip file can then be
distributed to whomever, however.  It is relatively simple to extract the
zip files, via java.util.zip, and display them in javasoft's JFC/Swing
componenets for viewing and manipulation.

Quite powerful!

Evan Vaala

Shawn Gordon wrote:

> ODBC/32 is the only ODBC driver that directly accesses Image, the others
> all go through Allbase (or Image/SQL if you will).  The full version of
> DataExpress has an ODBC that will directly access image, but that isn't
> what comes as part of the OS.
>
> shawn
>
> "Simonsen, Larry" <[log in to unmask]> on 11/06/98 02:11:20 PM
>
> Please respond to "Simonsen, Larry" <[log in to unmask]>
>
> To:   [log in to unmask]
> cc:    (bcc: Shawn Gordon/IS/FHM/FHS)
> Subject:  odbc
>
> Is there a good comparison between ODBC drivers for turboimage?  A
> comparison of features?
> ------------------------------------------------------------------------
> Larry Simonsen          Phone: 801-489-2450
> Flowserve Corporation   Fax: 801-491-1750
> PO Box 2200            http://www.flowserve.com
> Springville, UT 84663   e-mail: [log in to unmask]
> ------------------------------------------------------------------------

ATOM RSS1 RSS2