On 17 October 2014 15:43, Victor Gil <[email protected]> wrote: > If the CONNECT statement is successful: > • All open cursors are closed, all prepared statements are destroyed, > and all locks are released from the previous application server. > • The application process is disconnected from its previous application > server, if any, and connected to the identified application server. > • The actual name of the application server (not an alias) is placed in > the CURRENT SERVER special register. > • Information about the application server is placed in the SQLERRP > field of the SQLCA. If the application server is an IBM® product, the > information has the form pppvvrrm,
It's not obvious to me that a DB2 "application process" is a TCB. Sure, maybe it is, but then you'd think they'd call it that, or perhaps a task. "An application process" sounds more to me like an abstraction for DB2's purposes of some kind of run unit - process, thread, task, address space. Think about CICS; surely it runs multiple users, each with quite different DB2 contexts, under a single TCB? It must have some way of maintaining an "application process" for each user. What about Language Environment enclaves? This sounds like something similar; by default an MVS TCB is its own enclave, but it can certainly support more than one by using the LE anchor block support. But I really know almost nothing about DB2, and it's been decades since I last used its closest relative, SQL/DS, so I may be quite full of it. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
