|
Jon, Since you need it to work on older releases, return values, and want a simple call, and want to avoid JNI, nothing is going to be ideal. The challenge is the bi-directional parameters. The data queue is reasonable and not too hard to code, but not as simple as keying in a parameter name. You can also pass values through environment variables, a file, a user space or ? Since you will probably want to do this for a number of programs, why not just bite the bullet and build a call wrapper that handles the parameters for you? The iSeries-toolkit has some basic data queue support. You could create a procedure that puts an entry on a keyed outgoing data queue with a key of job number and program name with your outgoing parameters and then calls the java program. It would then sit on an incoming data queue waiting for the response. I have a more involved version of this that I could cut down but I don't have a lot of time to do this right now. David Morris >>> Jon.Paris@Partner400.com 05/30/02 10:38AM >>> >> I would second the recommendation of a queue for any call intensive operation. The trouble is it isn't call intensive and I just need the simplest approach possible. DQs and all the rest are great but total overkill for the application in question. Jon Paris Partner400
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.