Another option is to use Quest's NetBase Client.

NetBase Client consists of complete Application Program Interfaces (APIs)
that give UNIX, DOS, Windows, Windows NT and Windows 95 client/server
applications read and write access to data residing in MPE files, KSAM files
and TurboIMAGE databases on HP 3000 computers. By using the NetBase Client
APIs with Oracle, Informix, Sybase, COBOL, Microfocus, Excel, Visual Basic,
PowerBuilder, or any of the other DOS/UNIX/Windows tools available, your IS
staff can quickly implement applications that are tightly integrated with
existing HP 3000 systems.

Optionally, You could use BridgeWare to post changes, as they occur, from
the 3000 directly into an Oracle or SQL Server DW for access by your PC
clients.

Please let me know if you would like further information.

Allen Cintron
Quest Software
"Expect a Solution"
949-718-2454 direct
800-306-9329 X2454

-----Original Message-----
From: Shawn Gordon [mailto:[log in to unmask]]
Sent: Wednesday, September 30, 1998 1:05 PM
To: [log in to unmask]
Subject: Re: Making IMAGE data available to PCs


I have used both ODBC/32 and MiddleMan from MiniSoft to develop
client/server applications against both Image and KSAM files, and it works
great - very fast, easy to code, etc.  I would say that the only down side
is that the documentation is a bit on the terse side, but it's a great way
to go.

shawn






"Calandra, Jack" <[log in to unmask]> on 09/30/98 12:00:52 PM

Please respond to "Calandra, Jack" <[log in to unmask]>

To:   [log in to unmask]
cc:    (bcc: Shawn Gordon/IS/FHM/FHS)
Subject:  Making IMAGE data available to PCs




        I would like to throw something else into the mix.  How would
native
mode KSAM files fit in.  I have a third party payroll system that uses NM
KSAM files as the database rather than IMAGE.  We have been debating which
is the best way for users to access payroll/HR data from this system for
both reporting and inquiry purposes. One school of thought is to create a
DW
by extracting data from the Payroll System using tools provided by the
vendor. The problem with this, for us at least, is that payroll data is
constantly being updated to the KSAM database through the third party
package and users want up to date info.  So the DW concept,  is not the
best
way to go for us.

        My other thought is to use ODBC to connect directly with the KSAM
database and create a client server front end with something like Visual
Basic.  This way there would be dynamic access to the KSAM database and the
users would be happy.  There must be trade off's.

        I would like to hear from some of you regarding your experiences
and
opinions.

        By the way these KSAM files are very large, approaching the 4gig
limit and we run on a 3k 987sx.  No problems with CPU utilization or disk
space.  This box hax 1.5 gig of memory so at this point the system is quite
stable.  But what would happen if I add an Image database for the DW.


        Thanks in advance

        Lets keep this thread going!

        Jack Calandra
        System Manager
        AIG HRIS