Re: Applications with exit programs

On 08-Jun-2010 11:15, James H. H. Lampert wrote:

We have an application that currently uses a Java client
communicating (via a proprietary protocol over TCP/IP) with
an ILE server (mixed C and RPG). (It evolved from one with
a Smalltalk client and an OPM RPG server, which initially
communicated over APPC/APPN.)

The server has several exit hooks built into it, for both
security and integration with other applications. More
specifically, there are hooks on incoming client requests,
that can modify them, or propagate data from them into other
applications, or block them entirely, and hooks on server
responses, that can censor the data, or propagate it to other
applications.

We are contemplating the possibility of re-engineering this
application to use SQL through the Toolbox classes. But is
there a way to do this and keep the extensive exit program
capabilities?

IMO moving to the generic servers from the private server will likely be a significant effort and probably determined best to be implemented using SQL stored procedures anyhow, both for security and performance reasons. So perhaps keeping the existing server but changing that server-side code to generate SQL result sets which then can be consumed by the client, would be the easiest. That is, since all of the existing /hooks/ would remain effectively the same when using the existing server, there should be no need to figure out how to implement those /same/ hooks via the generic servers.?

FWiW the client /special registers/, available with DB2 for IBM i 6.1, might be useful in implementing exit points within the generic [perhaps only the database\SQL] servers for the client requests.

Regards, Chuck