Re: Free up Temp Addresses and unprotected space used

I got that guideline off IBM or maybe even an IT Jungle or similar article.
These days 10% or more would not alarm me; It seems to be a little bit
aligned with how much SQL is being used. Systems with loads of SQL/ODBC
type jobs seem to run quite a bit higher than 5%. As I said, I look for it
growing consistently over a period of time to indicate an issue. My
experience is it will generally level out at a different percentage for
each system.

30% for temporary addresses does sound a lot, but I confess I have not even
looked at that measurement for ages.

On Fri, Feb 22, 2019 at 12:11 PM Christopher Bipes <
chris.bipes@xxxxxxxxxxxxxxx> wrote:

I see percent of temporary address approaching 30%, never seen it that
high.
I guess the temporary storage 2511G total storage / 196867M temp is only
7.8% so that is within the guideline you specified. Again never seen it
that high. But our storage is now above 78%. Time to search for the
guilty IFS dumps that have eaten my storage.

--
Chris Bipes
Director of Information Services
CrossCheck, Inc.

707.665.2100, ext. 1102 - 707.793.5700 FAX
chris.bipes@xxxxxxxxxxxxxxx
www.cross-check.com
Notice of Confidentiality: This e-mail, and any attachments thereto, is
intended only for use by the addressee(s) named herein and may contain
legally privileged and/or confidential information. If you are not the
intended recipient of this e-mail, you are hereby notified that any
dissemination, distribution or copying of this e-mail, and any attachments
thereto, is strictly prohibited. If you have received this e-mail in
error, please immediately notify me by e-mail (by replying to this message)
or telephone (noted above) and permanently delete the original and any copy
of any e-mail and any printout thereof. Thank you for your cooperation
with respect to this matter.


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Evan Harris
Sent: Thursday, February 21, 2019 3:03 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Free up Temp Addresses and unprotected space used

Hi Chris

which of these do you want to "free up" and why ?

If it is temporary storage, how much temporary storage is your system
actually using, is it really excessive ?

-- My notes for calculating whether this is bad or not are as follows:
-- From the Current unprotect used field, determine what percent of the
system is comprised of current temporary space allocation through the
following formula:
-- % of temporary space consuming system storage = -- (Current unprotect
used in M bytes / Total ASP in G bytes) / 10.

-- If this value is higher than it should be, you may have a temporary
space problem - for most systems, 5% or less is normal.
-- The Maximum unprotect field allows you to get an indication of how much
temporary-- space has been allocated since the most recent IPL.
-- Keep in mind, it is not what is currently allocated in temporary space,
but a "high water" mark.
-- Substituting the Maximum unprotect for the Current unprotect used in the
formula above shows the amount of temporary storage that has been consumed
at one point since the most recent IPL.

I am not sure how accurate the 5% guideline is these days, but generally I
look to see if the temp stg is constantly increasing which might indicate a
memory leak and possibly a PTF being required.

This page:

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/Temporary%20Storage%20Consumption%20and%20DB2%20for%20i

has the following SQL to deterine the top 10 temporary storage consumers:

WITH TOP_TMP_STG (bucket_current_size, bucket_peak_size, q_job_name) AS (
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
FROM QSYS2.SYSTMPSTG
WHERE job_status = '*ACTIVE' AND
JOB_NAME IN ('QZDASOINIT', 'QZDASSINIT', 'QRWTSRVR', 'QSQSRVR')
ORDER BY bucket_current_size desc fetch first 10 rows only
)
SELECT bucket_current_size, bucket_peak_size, q_job_name,
V_SQL_STATEMENT_TEXT, B.*
FROM TOP_TMP_STG, TABLE(QSYS2.GET_JOB_INFO(q_job_name)) B

I guess ending the jobs should reduce the associated temporary storage.

--
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@xxxxxxxxxxxx for any subscription related
questions.

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