Today’s post discusses two APAR fixes; one a year and a half old that attempted to resolve a function’s incompatible migration behavior (PM29124) and a much newer fix that performs some additional resolution to that same incompatible migration behavior (PM66095).
DB2 V8 is out of service, DB2 9 is old news and end of marketing has been announced, and moving to DB2 10 is the “in thing” to do. If you have been keeping score, you know that all this activity usually means something else is probably going to occur… and it did.
I wanted to talk about the DSNZPARM keys deprecated in DB2 10. And yes I do realize that I listed them out in a previous post. However, this time I wanted to discuss why it’s important today, maybe even before migrating to DB2 10, to plan on how their eventual departure from DB2 may affect you.
Then someone pointed out to me that sometimes when we say something is “deprecated” in a future release of DB2, it can sometimes get misinterpreted, or misunderstood. In fact, there has been extra verbiage added to the DB2 10 Installation and Migration Guide (GC19-2974) to help alleviate future misunderstandings…… Continue reading »
Well, it’s been a good run… but all good things must come to an end.
DB2 Universal Database for z/OS Version 8 (5625-DB2), DB2 UDB for z/OS Version 8, or more conveniently DB2 V8 first peeked out at us on January 31, 2003 when the beta program began and arrived full force on the world when it went generally available (GA) on March 26, 2004…… Continue reading »
John did a 2-part webinar February 21-22 on DB2 10 migration (DB2 10 Migration Planning and Very Early Experiences – PART 1 & PART 2).
On Slide 22 of Part 2 of his presentation he discussed that two popular methods for capturing documentation on SQL for IBM (the popular part are my words, not his), DB2PLI8 and Optimization Service Center (OSC), are not supported by DB2 10 for z/OS…… Continue reading »
This is just a reminder to register for the upcoming “IBM DB2 10 Migration Planning and Very Early Experiences – PART 1 & PART 2” webcast. The webcast first part is tomorrow, February 21, with the second part on Wednesday, February 22, 2012. This is a no-charge IBM webcast with one of the best DB2 for z/OS speakers…… Continue reading »
DB2 for z/OS Version 8 goes out of SERIVCE (End of Service) on April 20, 2012, just three months from now.
DB2 10 once again offers a skip level migration from DB2 Version 8 to DB2 10.
DB2 9 for z/OS has announced its END of MARKETING as of December 10, 2012 and we all know that when we stop marketing a product, its End of Service announcement can’t be too far away…… Continue reading »
I came across something today that I was going to say was new, however, it may only be new to me…. it’s a PDF file of cumulative ++HOLD data that must be applied to DB2 10. This is pretty cool. This PDF has all the actions that must be taken if you used the new product tapes for DB2 10…… Continue reading »
DB2 10 has been around for a year now. Everyday we hear of another customer starting their migration planning process. With that in mind, I thought I should mention what the minimum requirements are to upgrade to DB2 10 for z/OS. Some of the requirements, like operating system level and machine type, are not things you can “just take care of” over a weekend. It’s almost as though you need a plan for what has to be completed before you can implement you migration plan. That stuff you need to start thinking about today is today’s topic of discussion…… Continue reading »
It was way back in DB2 9 that temp work files and sort work files were combined, or converged as the Redbook explains it. It all seemed like a good idea at the time, and it probably was, but there were still a few issues with the original implementation that have just been recently worked out last summer. The particular issue resolved last summer also just happened to be something I had the opportunity to experience first hand. Unfortunately, the fix wasn’t available at the time. Fortunately, we picked up on the error early on so when we had the problem we were able to immediately fix it…… Continue reading »