Hi,
I's like to share some experiences we had with Ondemand since we implemented DB2 V10.
A few months ago we installed V10 on our production system with OnDemand. After a few weeks we noticed a large increase of CPU-usage of the ARSSOCK task. The CPU almost tripled. Soon we found out it was all CPU executing SQL.
We did all of the standard recommendations in the V10 books like RUNSTATS with all the new options. Rebind the ODBC packages and the ARS* packages. But no improvement.
But the solution at the end was to bind the DSNCLINF package with the REOPT(ALWAYS) option. CPU consumption went back to normal.
We also tried REOPT(AUTO). But then we struck an open APAR (which might be solved in the meantime).
I don't know if other sites have the same experience.
Vriendelijke Groeten / Kind Regards,
Leo de Jong