On Wed, Dec 16, 2015 at 10:40 AM, Mike Schwab <[email protected]> wrote:
> > 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. Sombody should "Gibbs slap" them! RSM == "Real Storage Manager" to me. I doubt it is a part of DB2. Just out of curiosity, what does RSM mean in DB2 terms? Any why would a z13 do something different? > 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. > > -- Schrodinger's backup: The condition of any backup is unknown until a restore is attempted. Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
