Prevent package invalidation after ALTER TABLE ROTATE
System: Production management database
Actor: Developers maintaining the database
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.