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.
Prevent package invalidation after ALTER TABLE ROTATE
System: Production management database Actor: Developers maintaining the database Description: Our customer runs a 24/7 production management OLTP system with IMS V10 and DB2 V9 for z/OS on which its transaction rate gets as high as 10 trans/sec, and the production data must be retained as long as 36 months.
Tables are partitioned by range and each partition represents a container for a particular month which is specified by the LIMITKEY. Each table consists of 37 parts and a partition of the oldest month is to be rotated every month with ALTER TABLE ROTATE command.
Applications are running through the ALTER ROTATE process which includes invalidation of the packages. Under its high transaction rate, autobind of invalidated packages often causes contention of system resources such as the system catalog tables, SKPT and BINDLOCKs which results in transaction abends or inoperative packages.
Customer expects packages remain valid after rotation to meet their 24/7 requirements.
Do not place IBM confidential, company confidential, or personal information into any field.