Testing for the forth service pack of 2013, RSU service package RSU1304, is now complete. This May 2013 1st Quarter quarterly report First Addendum contains all service through the end of December 2012 not already marked RSU. This service also includes PE resolution and HIPER/Security/Integrity/Pervasive PTFs and their associated requisites and supersedes through March 2013.
The April 2013 product publication updates are now available. There were no updates for DB2 10 or DB2 9 for March 2013. The “almost new” tradition continues with the pub folk publishing documentation updates on a near monthly bases….. Continue reading »
DB2 10 for z/OS is just loaded with little gems. So many so, that sometimes I just mess up their descriptions. That’s what happened during my IDUG presentation today on a DB2 10 EXPLAIN feature. I took two very cool concepts delivered by DB2 10 and reversed their descriptions: EXPLAIN (ONLY) and EXPLAIN PACKAGE. Thanks to the two folks that were in my session today who caught my attempted confusion.
I’ve been a fan of IBM’s Redbooks for, I don’t , maybe as long as I can remember having a need for up-to-date information. That’s long enough to remember when the Redbooks still actually had Red covers. In fact, I’ve been a Redbook fan long enough to remember what a thrill it was when my IBM SE brought them to me back when I was a customer. I always thought I was special because he always brought me the latest Redbooks. Those books were a bigger deal than being taken out to lunch.
If you grew up in the US, you probably remember the round navy blue container with the little girl and umbrella on it spilling salt behind her. The phrase until the picture was “When it rains, it pours”. I think we have since lost sight of the original intent with this cute play on words… which refers to salt pouring freely in damp weather. Today we use it to describe a situation when you have too much and suddenly have even more.
It looks like I’m in for a slightly busier May this year, more like the old days, before my travel slowed. In fact, for some reason I find myself humming the old Huey Lewis And The News tune “The Heart Of Rock And Roll”… And yes I do realize the cities don’t match, well at least not until the last few words of the song.
My first trip will be to sunny Florida and the city of Orlando.
I’m still talking about real-time statistics. This is what is referred to as the trickle affect. Periodically I keep discussing another little piece of real-time statistics. This stuff is important… it’s useful… and in my opinion it’s pretty interesting…. Every time I reread one of my posts, I think of something else I should have said.
Now it’s time to discuss managing index usage via real-time stats.
An interesting title for a blog post? The word “update” implies I have discussed real time statistic before; I have not. Although, I wish I had. In fact, it’s getting ever more difficult to come up with an original DB2 for z/OS subject to write about. It sometimes seems like everything has been done, been discussed, been explained; and at least a couple of times by now. This blogging stuff was so much easier when I had the only blog that covered DB2 for z/OS. Now there are a bunch of these blogs; they’re everyplace. Unfortunately, I must admit that a couple of them a pretty good. It’s difficult for me to write about something that someone else has already done a great job describing.
Today’s blog post is a continuation of my earlier post on real time statistics (“An update on Real Time Statistics”) made just last week (March 21, 2013). Continuation is my way of saying I forgot to mention something that I really should have mentioned to make my real time statistics conversation more accurate. I didn’t discuss the relationship between DB2’s utilities and real time stats.
Once again I was asked about DSNDB01.SPT01 compression in DB2 10. Some still remember a few commits made just as DB2 10 became generally available (GA) discussing how SPT01 compression wouldn’t be needed in DB2 10. Those first comments were based on the fact the a lot of the information in SPT01 was being moved to large objects (LOBs) and LOBs cannot be compressed. If SPT01 data was being stored in LOBs and LOBs can’t be compressed, there would be no need for compression.