Re: SQL stored procedures and activation groups via JDBC

Hi, Nathan:

Thanks for your reply. It makes sense to me. But, as I said in my reply to Elvis, it is a vendor client/server application.

It was apparently written to be "platform-agnostic", so it can run on other platforms with other databases ... I believe the overall design was done and the product implemented on other platforms, and then they attempted to make the existing design work with DB2/400 and run the back-end on OS/400 or i5/OS, apparently with "mixed" results.... from what I can tell. (Strictly my own opinion.)

The customer is looking for ways they could perhaps make some small "adjustments" (or tweaks) to the application, to try to improve the overall response times, etc., without a total rewrite, which is out of the question, because it is not their application, it is a vendor package, so they do not have a lot of control over this. They can ask the vendor for assistance, and the vendor apparently will listen to ideas and suggestions that are i5/OS specific, and take that into consideration. I suspect this vendor does not have much OS/400 expertise "in house" ...

Cheers,

Mark

> Nathan Andelin wrote:

From: Elvis Budimlic
Why do you need to "clean up" these programs?

I know your question is for Mark, and I'd be interested in hearing his response too, but consider an application like the following:

http://www.radile.com/rdweb/temp/org100.html

The screen depicts a Note which is associated with a Person who is associated with an Organization. But the point is that as a user activates and drills down into tabs, more and more resources are dynamically allocated, and the job's call-stack may lengthen.

If a user were to activate all tabs over time, the application would open about 20 database tables, load about 120 HTML templates into memory, activate about 20 *PGM and 150 *SRVPGM objects, each allocated dynamically - when used.

But see the "Exit" link in the upper-right area of the screen. When that link is clicked, the *JOB associated with the application ends, so all its resources are released, and a portal menu or another peer application (if peer applications are active) is given control.

It may be old fashioned, but it seems reasonable to me to allow users to participate in the allocation and release of system resources.

Nathan.