Data Conversion

What might you think that all of the above have in common? They all play some roll in a behavior change that took place (or will take place) when you upgrade to DB2 Version 8 for z/OS. This one is not only kind of subtle; it's not even documented (yet) in the DB2 Version 8 manuals, depending on which copy of the manuals you look at (a good example why you should always download the most current

Do I have a deal for anyone just starting to plan their Version 8 upgrade or just starting to execute their Version 8 upgrade plan. For the last 2+ years I have been blogging DB2 for z/OS Version 8 upgrade tips. Some have been to help you plan your upgrade and some have been advice on what do to during your upgrade. I've discussed compatibility mode (CM), enabling new function mode (ENFM), and new

You are now running in DB2 Version 8 new function mode (NFM). Take a deep breath and give yourself a good pat on the back. You did good. However, completing your upgrade to V8 NFM really means that it is time to start planning your next upgrade, your upgrade to DB2 9 for z/OS. You see, all of the work you have just completed as put a new DB2 infrastructure in place. You have started to move

With every release of DB2, additions are made to the list of reserved words in the SQL Reference manual (for DB2 9 it's  SC18-9854 with the latest version as of this writing

You may remember back on July 13, 2007 in a post called  

And how do I know that? For starters, I just finished reading a paper by Julian Stuhler of Triton Consulting titled "DB2 9 for z/OS - Data On Demand" . If you know someone who needs a nice concise "to the point" description of the value of DB2 9 for z/OS, this is definitely the paper they need to read. Julian did a similar paper 3+ years ago on DB2 for z/OS Version 8 that was equally impressive.

Building on the excellent storage usage introduced in DB2 for z/OS Version 8, DB2 9 for z/OS has made more significant storage improvements of its own by moving more of the environmental descriptor manager (EDM) cache areas above the 2 GB bar. In Version 8, the "old" EDM pool was broken into three parts, or three distinct caches. All DBDs are now stored in the DBD pool (EDMDBDC) above the 2GB bar

If you're a z/OS person (or still refer to yourself as an MVS System Programmer) I can almost guess what goes through your mind every time you find out that there is a new version of DB2 available to install. You think "new version means new EARLY code means another IPL of my system". As long as DB2 for z/OS has been around, an IPL has been required to "activate" the EARLY code. As long as there

I'm talking about planning for your next DB2 for z/OS upgrade. With many of you already running DB2 Version 8 for z/OS, it's time to start getting ready for DB2 9. Yup, I'm suggesting that you start preparing your DB2 Version 8 for that eventual upgrade to DB2 9. It doesn't matter if you are migrating next week, next month, or two years from now. There's always going to be something that you