We have several unloads that use HPUs with SUPPORTED select that download UTS PBG.
Queries are unfortunately written by programmers who can change them independently and often don't know how many rows they will have to download and therefore they don't know if it is more convenient to use SQL MODE or NATIVE MODE. Often we have queries that with SQL MODE would be optimized with the use of indexes but using as default DB2 YES HPU decides to use NATIVE MODE and scans all the vsam consuming a lot of cpu and very high elapsed times to download a few lines.
Now when we intercept these cases we ask the programmers to use DB2 FORCE
We opend pmr 15863,830,758 but we were told that hpu works as it was designed
|Who would benefit from this IDEA?||With this proposal we would have better performance with lower CPU consumption and reduced elapsed|
How should it work?
HPU if supported query should explain the query and decide according to the access path and statistics when it suits them to use SQL NATIVE MODE or MODE
|Priority Justification||Reducing consumption is one of our top priorities|
|Customer Name||Intesa Sanpaolo|
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 "firstname.lastname@example.org" 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