Brian wrote:
In reviewing various documents a lot of them point to
creating a new subsystem and pushing the QZDASOINIT jobs onto it<<<<<.
I guess it's something we'll have to investigate once the new box arrives.


Isolating the QZDASONIT jobs to an "ODBC" subsystem with its own memory pool is probably going to fix your problem.

Here are the instructions provided by Bryan Dietz for isolating QZDASOINIT jobs:


Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact