Frank's right, Samba/iX and/or NFS would work. However to achieve the
real-time effect I think each transaction would need to be in a separate
file. Another option would be ODBC, or better still IPC sockets. Using IPC
sockets you could write/code directly into an existing process on the client
(9k) side to send a transaction record to the server (3k). This would
require you to write a server process on the 3k that is always ready and
willing to receive and process transactions, and send acknowledgements back
to the 9k client in real-time!

I worked with Net Partners ( a company here in Houston ) to help finish up
the MPE side of a system like this, using IPC sockets.  A brief summary of
the project can be read at

 http://www.npartners.com/projects.html#MainFNetInt


If you need any more info or would like to contact the guy responsible for
most of the detail design, send email to me at [log in to unmask] or Net
Partners at [log in to unmask]


Regards,
Michael Anderson





Ewart North wrote:

> Dear Friends,
>
> I have an application running on an HP9000 which needs to post data into
> a financial system running on the HP3000.  I can create files of posting
> transactions on the 9k, ftp them to the 3k and post them, all in batch
> mode, no problem.
>
> My user is now saying "why can't we do this on a transaction by
> transaction basis?"  I think what he means is to closely link the two
> systems so that the SOP (9k) checks codes which exist in Image on the 3k
> so that mis-postings can be eliminated earlier in the processing cycle.
>
> My questions-
> Is this scenario possible?  If so what do I need on each machine to
> accomplish this?
> What are the consequences (if any) for response on either or both
> machines?
>
> Help really appreciated.