|
We have begun to experience a higher than normal rate of jobs that
fail to end.
Here is the scenario...
We have a scheduled job that will spin through the active pre-start
jobs (in our case: QRWTSRVR jobs that service our web consumers) with
OPTION(*CNTRLD). After a time, the OS will usually turn around and
end them *IMMED...usually.
In some cases, for an unknown reason, the transition from *CNTRLD to
*IMMED does not seem to occur. When this happens, the only way we've
found to kill them off is to do an ENDJOBABN.
The program stack shows that they are in the process of some DB
cleanup.
The stack includes: QSQXIT (procedures: CLOSE_IT and QSQXIT), QSQBAS
(SQHRDCLS), QDMCLOSE (statement /0113), QDBCLOSE (statement /02B9),
QQQQEXIT (procedure QQQQEXIT and TIDYUP).
My questions...
Has anyone else experienced this?
If so, were you able to discover why (in our case, the number of
incidents increased since last weekend's build install, suggesting we
somehow contributed to the problem)?
Is there a cure?
I can find nothing that seems to address this in the archives.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.