On 16 October 2014 14:00, Victor Gil <[email protected]> wrote: > 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.
I've been pondering these task matters, but it strikes me that this may be entirely the wrong approach. I don't know DB2, but I'd be a little surprised if it keeps track of connection attributes (cursors, locks, etc.) only at the TCB level, and doesn't have any mechanism to maintain independent connections at a lower level. Surely there is some kind of "object" or control block or the like that can be instantiated more than once in an MVS task that can represent these things. Is it not possible, e.g, for a server to handle multiple users each with their own connection to DB2 using a single TCB? Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
