Re: qtemp performance oddity. -- MIDRANGE-L

× 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.

That MF26466 may have been what changed QTEMP libraries to temporary objects; I seem to recall the decision about temp vs perm was related to the security level. If so, do not apply that PTF; regardless, the latest is best applied, typically. So... apply the supersede MF28377, which if the former makes the QTEMP libraries temporary, presumably the latter changes the code back to making the QTEMP libraries permanent.

I wonder what the MF28377 cover letter says.

Regards, Chuck

On 28 Feb 2013 12:43, Bryan Dietz wrote:

OK, so I downloaded the cover letter for MF26466

DESCRIPTION OF PROBLEM FIXED FOR APAR MA22147 :
-----------------------------------------------
Some applications such as SQL create several objects in QTEMP
and then later remove them. <<SNIP>>
CORRECTION FOR APAR MA22147 :
-----------------------------
This PTF reduces the number of disk writes done to QTEMP
libraries.<<SNIP>>

CIRCUMVENTION FOR APAR MA22147 :
--------------------------------
Run the system at security level 50.

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.