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

The best way to demonstrate temporary storage growth and prove you are losing disk space to temporary storage utilization is to use historical data.
If you have a memory leak, memory gets paged out to disk because it is never freed and you will see your temporary storage utilization increase.

Historical data collection is available in 7.3 and later; it is not on by default, you must change the Collection Services Configuration to enable historical data collection. Then, whenever Collection Services is cycled, the historical data from that collection will be included in the historical summary and detail data.

Once you have historical data collection enabled, you can view that data with Graph History (an option in the Performance Tasks in Navigator for i - it is available in New Nav).
Graph History allows you to review a select set of metrics over a potentially long period of time (days/weeks/months/years).

One of the metrics that you can view using Graph History is Temporary Storage Utilization. When you have a temporary storage issue, it will be clear in the temporary storage utilization trend line.
If that line is always going up, you want to know why and get the issue resolved.

In addition, with Graph History, you can click on a point and see the top contributors, which will be job names. This **might** give a clue as to the source of the problem.
For example, at any given time, the temporary storage used by a job or group of jobs may seem small, but with the summarization done in the historical data, for a 6-hour timeframe (for example), that guilty job(s) may very well pop to the top of the list.

In my opinion, an IPL, while it will free the temporary storage, is not a solution.

I have several iCan blog posts on historical data as well as using the performance tasks to understand disk space utilization.
Please refer to the following:





From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Rob Berendt <rob@xxxxxxxxx>
Sent: Tuesday, August 9, 2022 1:27 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Memory used by *MACHINE

Actually that's per week, not per day.

According to IBM: ... it would appear that your system is doing very well on temp storage and no corrective action is required.

1% is 1% of total space. Of a 1.8TB system.

Roundabout 18GB/day. That's seems a lot!

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
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

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