|
That may be the result of the SQL statement in the iSeries not optimizing (it can happen from changes in the database such as number of rows in tables, dropping indexes etc.).
I would recommend investigate into the QZDASOINIT jobs as follow:
- Force debug messages by setting parameter MESSAGES_DEBUG to *YES in the qaqqini file
- Force the joblog to print by temporarily changing the job description.
The joblog will show you the SQL used, how much time every statement taken, and the access plan (How did SQL planned to get the records).
|
