I'm looking at PRTDSKINF. When I do some comparisons with previous runs we're losing about 1%/week due to temporary storage. Actually our biggest loss on that report. Not our biggest consumer, by far, but our biggest change. No ERP like stuff on this lpar therefore no 'query from hell' scenarios.

Run SQL Scripts has a nice example on how to analyze temporary space. I ran it stock with the only changes being commenting out the where clause and adding all columns.
SELECT bucket_current_size, bucket_peak_size,
rtrim(job_number) concat '/'
concat rtrim(job_user_name)
concat '/'
concat rtrim(job_name) as q_job_name, systmpstg.*
FROM QSYS2.SYSTMPSTG
-- WHERE job_status = '*ACTIVE'
ORDER BY bucket_current_size desc;

Results:
https://imgur.com/gallery/AkaGacP


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2025 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.