DB2 batch SELECT taking too long
Posted: Mon Oct 06, 2025 6:42 pm
Hello Forum,
I’m dealing with a report where a SELECT is driving up CPU. How do you usually approach profiling COBOL + DB2 queries—EXPLAIN, RUNSTATS, index review? What’s your go-to order of attack? Appreciate any ideas or examples.
I’m dealing with a report where a SELECT is driving up CPU. How do you usually approach profiling COBOL + DB2 queries—EXPLAIN, RUNSTATS, index review? What’s your go-to order of attack? Appreciate any ideas or examples.