DB2 to provide a way to override MAXPARTITIONS and LOCKSIZE defaults Merged

QMF Product Development is opening this work item in response to DeveloperWorks Request id 59512 (PMR: 46297,442,000) (RTC ID 41210). Please review that work item to see the customers pain points. We have had additional discussions with the customers and here are some questions we asked with their responses as to why they need to do implicit table space creations and why they would like to override certain parameters.
· Explicit table spaces are what we were using before we started converting/creating new QMF tables with implicit tablespaces.  There are multiple reasons why we need to stay with implicit creation vs. using multi-table tablespaces for QMF tables: 
1)  As a new standard policy in our shop, we are converting all multi-table tablespaces to 1 table per tablespace, including QMF. 
2)  Specifically for QMF, we use implicit table spaces to get 1 table per tablespace in order to prevent/reduce the large size of multi-table QMF table spaces (which end up containing 100s if not 1000s of QMF tables in each tablespace). 
3)  Using implicit tablespaces to get 1 QMF table per tablespace allows us to reduce contention, improve query performance,  and improve the efficiency and reduce the cost of QMF tablespace backups/reorgs/runstats which we run conditionally based on activity in the tablespace.  
4) Using implicit table spaces eliminates the exposure of someone accidentally doing a load replace on a single table in a multi-table tablespaces and consequently emptying out all the other tables (which has happened before and resulted in significant recovery and downtime for the users).    
5) The problem right now with the implicit tablespaces used by QMF (done by DB2) is that we have to do weekly mass ALTERs on 100s of implicitly created QMF table spaces to change the MAXPARTITIONS and LOCKSIZE as well as the BUFFERPOOL (we isolate QMF tables/indexes to their own bufferpool and implicit tablespaces do not use the default BUFFERPOOL settings defined in each of our QMF databases). We do not want to change our zparms since the global settings there controlling MAXPARTITIONS and LOCKSIZE for implicitly created tablespaces are correct for the majority of DB2 users, just not most QMF users.  Space is not the issue d'jour.