×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
We recently swapped out (upgraded) our hardware of our IBM.
Since then, when we IPL, we have jobs that "go nuts" and take up all the CPU in the QUSRWRK Subsytem.
We have to ENDJOB *IMMED them. This continues for a few hours, but after few hours later, this phenomenon stop happening.
These QUSRWKR jobs are created when other systems run SQL over the database.
We are almost positive this is due to the system deleting temporary file indexes when the IPL happens.
We are perplexed as to why did this start happening with the new hardware? Is anyone aware of a system setting or some other place that cause indexes NOT to be deleted as part of an IPL?
We know we can solve this by creation of permanent indexes. However, we have users writing their own queries at any time so we really don't have a way to prevent someone from writing a poorly written query that would just cause this to re-occur.
Thanks
Aaron
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.
midrange.com
