Our company uses DB2 zOS almost exclusively for dynamic SQL workloads. Our management expects that DB2 zOS also has high availability regarding DDL changes in this application szenario. If you intend to perform DDL changes in this environment during online operations, there are often impacts that go beyond the object to be changed. DDL changes such as DROPs of objects that are no longer required can lead to contention of other applications that have no connection whatsoever to the object to be deleted. This means that applications that are not directly affected by the change are also negatively affected by the change. If you analyze the interactions of workloads with dynamic SQL, you can often see that mainly the DBD design (a database forms a DBD and not a table) is the cause for the contentions. We expect a significant improvement in the current mechanisms of action with regard to DBDs similar to the transformation of the DB2 plan structure (transition from DBRMs to packages)
Why is it useful?
|Who would benefit from this IDEA?||Any company that needs to make DDL changes in connection with dynamic SQL workloads at online times should benefit from the idea.|
How should it work?
I have no exact idea how the improvements at the DBD design level should look like. In any case, the design change should lead to the fact that the change management of DB2 objects is really possible in time windows in which online operation takes place.
|Customer Name||Datev eG|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions