|
Jon Paris wrote: > > >> 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, for COBOL, you could have an RPG wrapper to handle the calls to Java. But once you've done the dataqueue stuff once, it's not so bad. And using the JAVA command means you never have to worry about classpaths, or garbage collection, or memory leaks, or inadvertent ending of the JVM.
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.