ftp://public.dhe.ibm.com/software/systemz/whitepapers/Whitepaper_Campbell_IML14294-USEN-00_Planning_for_IBM_DB2_10_for_zOS_Upgrade_October2011.pdf Page 11.
'Another point to remember is that when you use persistent threads with RELEASE(DEALLOCATE), there is a tradeoff. Doing so will impact BIND/REBIND and SQL DDL concurrency. When you have a high-volume transaction that justifies use of persistent threads with RELEASE(DEALLOCATE), then BIND/REBIND and DDL activity cannot break in.' RSM is a part of DB2. One option of BINDING (connecting the compiled SQL statement and program object code) is to keep the SQL code in storage until deallocated to save overhead. The side effect is other tasks can't BREAK in to access the database. I assume this APAR attempts to ease problems with a z13 hardware feature. On Wed, Dec 16, 2015 at 9:31 AM, Jake Anderson <[email protected]> wrote: > Hi, > > I was looking through the z13 and found about Memory management > optimizations of Bind Breaks for z13. > > http://www-01.ibm.com/support/docview.wss?uid=isg1OA46612 > > Can someone please explain on what is bind breaks ? > > Jake > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
