By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,610 Members | 2,310 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,610 IT Pros & Developers. It's quick & easy.

performance & behaviour question

P: n/a
I would like to have some information about the cooperation between DB2
Connect for .Net en DB2 data base for z/OS390.

We have a scenario where a .net client will call a DB2 Stored Procdure
through the DB2 Connect Gateway. In the stored procedure a cursor is created
and opened. Our .net application does the actual fetching.

The question is what happens with the cursor when the .net data provider
closes the DB2 Connect connection. Will the cursor be closed or will be kept
open because of the effects of Connection Pooling which keeps an DB2 Thread
running while waiting for a new client? Will there be a new cursor everytime
a .net client connects to call a stored procedure?


Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.