Well, I told you I wasn't a DB2 expert! <g> You can't share the other program's existing connection? Not do a new CONNECT, but just do whatever you have to do?
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Victor Gil Sent: Friday, October 17, 2014 12:44 PM To: [email protected] Subject: Re: How to quietly terminate not detached subtask Not reasonable at all! Quoting from the DB2 manual [watch the wrap] http://www-01.ibm.com/support/knowledgecenter/SSEPEK_10.0.0/com.ibm.db2z10.doc.sqlref/src/tpc/db2z_sql_connect.dita Successful Connection: 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, ... ================================== Sounds very reasonable. I would certainly think so. I am way less than a DB2 expert but I don't think any cursor type information is maintained in any sort of magic control block. Even a single simple COBOL program can be doing multiple logically independent things at the same time. There is a list where the people who actually are DB2 experts hang out: http://www.idug.org/p/fo/et/topic=19 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
