If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > ODPs related to non-native iSeries Database Connections

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-01-04, 17:12
ems2000 ems2000 is offline
Registered User
 
Join Date: Dec 2004
Posts: 1
ODPs related to non-native iSeries Database Connections

DB2 for iSeries. OS Ver. 5.2 running on an 890. My question is related to the high number of ODPs shown for our non-native java connections (i.e. ODPs within QZDASOINIT jobs). In researching this I find that these ODPs are part of DB2s work to keep pseudo-opens/closes on access paths for future use and that they can exist as long as the connection has NOT been closed by the application. I've also learned that the QAQQINI file has two settings - OPEN_CURSOR_CLOSE_COUNT and OPEN_CURSOR_THRESHOLD which can be used to manage the number of ODPs in the job. What I can't seem to find is information related to properly managing the ODP count in the job. As the ODP count increases is there a system level performance degradation? Is there any documentation that discusses the pros and cons related to taking the defaults for the QAQQINI settings or documentation that discusses considerations for setting these two QAQQINI parameters? Or if anyone has personal feedback, please let me know. Thank you very much.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On