Problem: A stored procedure takes about 1 to 2 minutes for the first invocation (No difference in this timing for green screen or i-series navigator or Java call through QZDASOINIT jobs). Subsequent invocations are wicked fast with subsecond response times
Other info: Procedure takes 1 input parameter and results a return set by opening a cursor.
Please let me know if this is because of plan or access paths being built every time for a new job? If yes, how can this be moved to the DB2 side so that the access path is shared across the jobs?
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!