Buck Hope we're not crossing posts here, but here goes. At 02:02 PM 12/3/1997 -0500, you wrote: -snip- >I have 2 identical databases, or, more accurately, I have one database >spread across 2 machines. One is an AS/400 and one is an NT server. >The AS/400 contains name and address information for end-users, >and the NT box has name and address information for vendors. >Here's what I *thought* I had to do to use data queues to communicate >from the Java client to the AS/400 (please excuse the terminology...): >1. In the Java client, call a routine that sends a request to the data queue >2. In the AS/400 server, receive the DTAQE, query the DB and send the > results back to the DTAQ >3. In the Java client, call a routine that reads the DTAQE, parses the > results and displays them. >Did I miss something? > >Now, my Java client's routine is writing to/reading from a data queue. >How can I use this identical code to get the exact same information >from the NT server? -snip- >>No. As long as the code is 100% Java, you can choose your client platform. >>The nit you are picking has to do with choosing to talk to a specific >>server. There is no requirement to. >In theory I guess I don't need to talk to a server, but where do I get my >data from if I don't? Not if your client talks _directly_ to the 400 or NT. But consider using a middleman server. Then your client talks to _that_ server, perhaps with some setting or parameter that identifies the backend server to talk to. The _middleman_ is the one that knows how to talk to every backend you have—your client needs to speak only to the data 'sales rep'. :-) -snip- Cheers Vernon Hamberg Systems Software Programmer Old Republic National Title Insurance Company 400 Second Avenue South Minneapolis, MN 55401-2499 (612) 371-1111 x480 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "JAVA400-L@midrange.com". | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.