We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Restrictions on ALTER TABLESPACE statements that cause pending changes:
ALTER TABLESPACE statements that cause pending changes have the following restrictions:
Options that cause pending changes cannot be specified with options that take effect immediately
Options that cause pending changes cannot be specified for the following objects:
Objects in a workfile database
An ALTER of PRIQTY is an immediate ALTER but the ALTER of COMPRESS is a pending alter and is not complete until a REORG is run. So when combined, the ALTER of PRIQTY is ignored. In this case, the ALTER of COMPRESS and PRIQTY should be done in separate DDL statements.
Though this is documented, it is doubtful most DBAs have reviewed the DOC that thoroughly. Since this action did not return a negative SQLcode, most DBAs would proceed under the assumption that the mixed DDL "took", and may not discover PRIQTY was lost until much later.
The DBAs need to be prompted to examine the documentation if they make an error in DDL such as this...I suggest a negative SQLcode be returned instead of allowing the operation to proceed.
Do not place IBM confidential, company confidential, or personal information into any field.