|
I'll respond with the ones i have experience or an opinion on. 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 actually, the opposite is true - disallow interactive queries (only allow batch) and interactive performance increases. 3. Keep spool files cleaned up I believe this has minimal effect on CPU performance one way or another, (although for every spool file, there is a dormant job attached, with it's associated overhead), but PERSONAL performance is enhanced when keeping spoolfiles cleaned up. 5. Minimize the number of jobs in the system minimal - with a caveat - if a job is sucking resources, don't let a bunch of them run at the same time, or let them run interactive - put them in a single threaded jobq to run in batch one at a time.
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
