Re: Bind Breaks for z13
In
Re: Bind Breaks for z13
And neatly sidestepped another pedantic war.. 3 cheers!!! Rob Schramm On Wed, Dec 16, 2015, 12:21 PM Jim Mulderwrote: > > 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 ? > > Bind Break is an internal serialization mechanism in z/OS. > It involves signalling the online CPUs, and does not complete > until all of the online CPUs have enabled for I/O and > External interrupts (not necessarily at the same time). > So its cost tends to rise as the number of online CPUs increases. > > This APAR changed data space delete processing in RSM > to reduce the number of Bind Breaks that RSM needs to do > when multiple jobs are doing DSPSERV DELETE concurrently. > > Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Bind Breaks for z13
On 12/16/2015 11:47 AM, John McKown wrote: 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? What he said. And now we have a reason for more pedantic wars. Regards Steve Thompson -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Bind Breaks for z13
> 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 ? Bind Break is an internal serialization mechanism in z/OS. It involves signalling the online CPUs, and does not complete until all of the online CPUs have enabled for I/O and External interrupts (not necessarily at the same time). So its cost tends to rise as the number of online CPUs increases. This APAR changed data space delete processing in RSM to reduce the number of Bind Breaks that RSM needs to do when multiple jobs are doing DSPSERV DELETE concurrently. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Bind Breaks for z13
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 Andersonwrote: > 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 lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Bind Breaks for z13
On Wed, Dec 16, 2015 at 10:40 AM, Mike Schwabwrote: > > 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN