I started writing this up a few days ago and got distracted. Since it’s Friday, I thought I would make it an installment of my APAR Friday series… although that was not the original intent. Originally, I just though this was a cool enhancement that’s going to make someone’s life just a touch easier…..
As you know, when you do a DB2 REORG against a partition table space, you can specify a range of partitions.. for example PART ( 5:10 ) or partitions 5 through 10. Handy, useful, and does make life simpler. However, what happens if you have multiple ranges, let’s say 5:10, 20:25, and 50:60? What do you do? You run (submit) multiple recoveries, right.
This set of APARs give you are comma between the ranges. I know it’s a lot more than that… but that is the syntax change. Rather than submitting three jobs to handle the above example, you can simply specify PART ( 5:10, 20:25, 50:60 ) to handle all three ranges in one job step. If for some reason, over lapping partition are specified, DB2 just eliminates them and only REORGs the partition one time. DB2 will also give an error should terminating the REORG if an invalid partition is specified.
All in all, a very handy utility change that I think should be very useful by most using partition table spaces.
This is a DB2 9 for z/OS fix only. I found nothing in the APAR that would make one think it also applied to DB2 V8. There are also two APARs you are going to have to track down and install in order to get this feature. They are:
Both APARs closed on July 23, 2010 and they are both tagged “Special Handling/New Function”. The PTFs for the above mentioned APARs are UK59095 and UK59096 respectively became available on August 14, 2010.