Tracking down temporary storage usage can be difficult. on 7.1 and earlier
releases.
This is an area where IBM made significant enhancements in the 7.2.
release.
Rather that write the details here, please see these blogs:
System infrastructure changes for improved tracking -
http://ibmsystemsmag.blogs.com/i_can/2014/06/72-improved-temporary-storage-tracking-part-1-.html
System-level interfaces for understanding temporary storage consumption -
http://ibmsystemsmag.blogs.com/i_can/2014/06/72-improved-temporary-storage-tracking-part-2.html
Job-level interfaces for understanding temporary storage consumption -
http://ibmsystemsmag.blogs.com/i_can/2014/07/ibm-i-72-improved-temporary-storage-tracking-part-3.html
Collection services and the performance data investigator support that was
added -
http://www.ibmsystemsmag.com/Blogs/i-Can/January-2015/IBM-i-7-2-Improved-Temporary-Storage-Tracking-(Par/
Part 5 will be on automated notification mechanisms added to monitor growth
of temporary storage use.
Dawn May
www.ibmsystemsmag.com/Blogs/i-Can/
From: John Yeung <gallium.arsenide@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 02/18/2015 10:40 AM
Subject: Re: Temporary space
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
On Wed, Feb 18, 2015 at 9:59 AM, Luis Rodriguez <luisro58@xxxxxxxxx> wrote:
Maybe I'm wrong but couldn't (as the article states) tracking your jobs's
behaviour be a help of how much temp space your system consumes? If so,
*maybe* you could avoid running your most "expensive" (in terms of temp
space) jobs simultaneously...
Luis, it's not that we're close to capacity. There's no point trying
to rearrange "expensive" jobs. None of the jobs is very expensive,
relative to the capabilities of the system. We could easily double or
triple our normal workload, and our machine would not break a sweat.
When looking at individual jobs, nothing looks out of the ordinary.
There are no obvious runaway or hung jobs, and no *obvious* disk
leaks. Yet every week, *TMPSPACE marches upward. The longer the
system is up, the bigger *TMPSPACE becomes. It's not like it ebbs and
flows. It just goes up.
Also, on our system, the "Current unprotect used" is always very close
(within a few percent) to "Maximum unprotect". *TMPSPACE, current
unprotect, and max unprotect basically go up in lockstep.
John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
midrange.com
