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



My educated guesses . . . I am sure I will be corrected is I speak out
of school <<grin>>

Note: in my case the primary indicators I use for performance are
interactive response time and job-queue depth.  These two together are a
reasonable measure of throughput.

1. Disallow queries from being run in batch
>> Interactive queries are a performance nightmare, particularly if
your system has interactive limits.  This will have a NEGATIVE impact on
performance.
>> If you mean the inverse (force queries to batch), it will have an
impact, the magnitude depends on how often interactive queries are run
now.

2. IPL regularly (weekly?)
>> b-negliglble -- depending on the current time between IPLs and how
often other system cleanup/maintenance is done.
--> You can answer this specifically for your system by scheduling an
IPL and measuring performance before and after.  If there is a
difference, then IPL regularly.

3. Keep spool files cleaned up
>> b-negligible unless there are a huge amount of spools now.  Old
spools are more a disk issue than a performance issue.  
--> That said, getting DASD usage below 75-80% will have a noticeable
impact on performance - that is one of those knee-of-the-curve
phenomena.

4. Change QPRFADJ to 0 and manually tune system
>> Will likely have a negative impact unless you are pretty good at
it.

5. Minimize the number of jobs in the system
>> I assume you mean to minimize the number of jobs in the system at
the same time . . . if performance is poor, this will likely have an
impact as it will effectively increase the resources available to each
job.

>>> M1C@xxxxxxxxxxxxxxxxx 02/19/03 11:02AM >>>
I asking you all for your opinions on how the following affect
performance,
overall and particularly interactive.

Respond with:
 a. Will make no difference
 b. Will make negligible difference
 c. Will increase performance noticeably
 d. Will increase performance dramatically


1. Disallow queries from being run in batch
2. IPL regularly (weekly?)
3. Keep spool files cleaned up
4. Change QPRFADJ to 0 and manually tune system
5. Minimize the number of jobs in the system


Thanks in advance. 

THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH 
IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL 
AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW.  If the reader of this message 
is not the intended recipient, or the employee or agent responsible for 
delivering the message to the intended recipient, you are hereby notified that 
any dissemination, distribution, copying, downloading, storing or forwarding of 
this communication is prohibited.  If you have received this communication in 
error, please notify us immediately via email and delete the message from your 
computer files and/or data base.  Thank you.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.