It is client's responsibility to close the database connection gracefully
once it's done using it. In this case, client is the WDSC application and
apparently it is not closing the database connection gracefully.
You should check if any WDSC fixes exist that would correct this issue.
In the meantime, you can still address the issue using brute force approach
as you have been, but be more granular about which database prestart jobs
you're killing. Since you're on V5R4, the WRKACTJOB display will show real
Current User for the QZDASOINIT jobs. Just kill ones that run under the
affected developer's profile, not any others.
Celebrating 11-Years of SQL Performance Excellence on IBM i5/OS and OS/400
I have searched the Midrange-L archives and I realize this topic has been
discussed a lot. I couldn't find a definitive answer. So I thought I would
see if someone can give me a quick & easy answer.
We are on V5R4. Our QZDASOINIT jobs run in QUSRWRK which has it's own
storage pool. My issue is these jobs stay in the system forever (or at
least until our next IPL) or so it seems.
The problem with this is our web folks have some SQL in Stored Procedures
which they run to extract data from the iSeries to build other tables on the
iSeries. Occasionally, when they are testing these, they run them from
WDSC. When they do this it seems to leave things "hung" in one of the
QZDASOINIT jobs. Even if the developer closed his pc down & reboots. If he
tries to rerun the process, it gets an error.
If I go manually end a bunch of the QZDASOINIT jobs, and I have to be
careful here because our website jobs come in through these jobs also, then
they can rerun their process.
I have often thought they are closing things correctly in their SQL
processes but I'm not fluent enough in SQL to know. After reading the
issues with the QZDASOINIT jobs hanging, is it something else?
Is there something I can be doing on the iSeries side to clean these up?
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact