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.
“Red Alerts” are serious and should be address in as timely manner as possible.
In this case, it all has to do with the ability to recover spacemap updates, are rather not be able to recover them.
Testing for the second service pack of 2013, RSU service package RSU1302, is now complete. This March 2013 4th Quarter quarterly report is the second addendum of 2013. It is based on the previous quarter and contains PE resolution and HIPER/Security/Integrity/Pervasive PTFs and their associated requisites and supersedes through January 2013.
Testing for the first service pack of 2013, RSU service package RSU1301, is now complete. This February 2013 4th Quarter quarterly report is the first addendum of 2013. It is based on the previous quarter and contains PE resolution and HIPER/Security/Integrity/Pervasive PTFs and their associated requisites and supersedes through December 2012.
A complete list of products and tools and their tested levels is available HERE.
Today’s blog post discusses two DSNZPARM keywords (MAXCONQN and MAXCONQW on the DSN6FAC macro) that were introduced on December 13, 2012 via APAR PM43293 to improve management of (distributed) database access threads (DBATS). However, before we (that proverbial group of nonexistent people that live in my head that always tend to volunteer me for stuff that always seems to get me into trouble) get into the details of these two new system parameters, I thought it would be prudent to review a few of the existing distributed terms (like DBAT) and a few DSNZPARM keywords that are used in APAR PM43293’s cover and in today’s blog post: MAXDBAT and CONDBAT on the DSN6SYSP macro and CMTSTAT on the DSN6FAC macro.
Here are a couple of blog post I have made to my Toolbox.com blog.
The first covers an upcoming webcast on DB2 futures by Jeff Joston…
Upcoming DB2 11 preview (plus other stuff) webcast with IBM’s Jeff Josten
The second one covers the latest maintenance RSU…
January 2013 (RSU1212) service package has been tested and is now available
Please check them out
2012 comes to an end today. Many have the day off, some don’t but aren’t getting much work done anyway, yet others still have things to complete to finish up their year. With all that in mind, I thought a short yet still handy post would be perfect to cap off the year.
Anyone who has ever messed around with tuning DB2 for z/OS has probably come across an IFCID (instrumentation facility component identifier) at one point or another. In fact, I did a blog post back in May 2010 discussing DSNWMSGS (Instrumentation Facility Component Identifier ) In fact, DB2’s IFCIDs have information on just about any DB2 for z/OS metric you could possibly be interested in, and new ones are added all the time and the current ones are always being expanded.
and “Musings of a Life-long Mainframe Guy” blog.
It’s the end of the year, the fourth quarter of 2012, and DB2 land has just “published” the last updates to the “Diagnosis Guide and Reference” (LY37-3220 for DB2 10 and LY37-3218 for DB2 9).
That’s right… I just didn’t care for the way it flowed… so I had a little time while eating lunch today… with a sandwich in one hand and keying with the other, I did a little patch work to a blog post I published back on October 28 that discussed the potential for wasting space in the older style table spaces after migrating to DB2 10.
Visit “APAR Friday: If you recently migrated to DB2 10, watch out for table spaces using too much space (HIPER) “ for the rewrite and what I think is a much better description of the issue. If you want, let me know if it reads better now.
I couldn’t decide whether to post this at first, thinking it might be too specific. Then I started getting (and reading) questions about stored procedure and figured you all had a delete button. For those not using stored procedure, you all can just skip this one.
However, if you are a big stored procedure user, you might want to check this one out. It’s marked as a “new function” for DB2 10.