Thanks! This would be a totally different ball game as it brings an extra layer of communication between the address spaces. This would also require extra "authorization" which wouldn't fly well with the management
=========================== >Working on a general purpose callable subroutine to connect to a remote DB2 >subsystem and return values back to the caller. > >Since the caller may [and WILL] have established its own DB2 connection to a >local DB2 subsystem, possibly with some cursors open and DB2 locks acquired, >the subroutine must run under a different TCB. You might consider going a bit further, and using fork() and execmvs() to create a new address space running your new code. That will isolate it quite well from the original task. And since you will not get control to signal it to terminate, it might do so after some period of time without hearing from you, say 5 minutes or whatever value you consider reasonable. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
