|
> From: NGay@xxxxxxxxxxxxx > > What about when the RPG has a few tables to open up and access? If you > called the same RPG program say 100 times, and the RPG program accessed > say > 5 DB2/400 tables, wouldn't it re-open those tables on every call? With an > RPG program calling another RPG program you can get it to keep the tables > open so you don't have this overhead each time but when calling from Java > isn't a totally new RPG environment on each call and so there'd be a huge > overhead every time of opening up all the tables? This is the kind of > thing which worries me about calling RPG from Java - not the speed of the > program call itself. This is an application design issue. You have several ways of keeping an environment stable if that's you're primary concern. You can keep the connection to the service job open, thereby ensuring that the same job is used and enabling all those features. Or, you can write server program and access them via data queues or sockets. Which direction you go depends on the nature of your application. The nice thing about server programs is that they can scale up immensely. And depending on your design, you can assign one job per session and end up with all the benefits of a traditional application (keeping state in the RPG program and so on). Joe
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.