RPGIV @ Work

A unique site for RPG and System i Lovers


Hi, this site will provide all what you need in System i and RPG developments.

My Name is Chamara Withanachchi, System i Expert and RPG Developer. And in the field for last 11 years.

I hope you will find lot of valuable information from this site

Temporary Space Print E-mail
User Rating: / 0
Written by Chamara Withanachchi   

The Work with System Status (WRKSYSSTS) command shows the current amount of temporary storage being used as "Current unprotect used", while the "Maximum unprotect" value is the high-water mark - showing the highest value temporary storage has reached since the system was last IPLed.

Temporary storage is only allocated from the system Auxiliary Storage Pool (ASP) rather than all ASPs.

To determine if a temporary space problem exists, use the WRKSYSSTS command and the following values:

tem Status                    S65D8902
                    31/12/10  08:09:59
 Auxiliary storage:                   
   System ASP . . . . . . :    701.6 G
   % system ASP used  . . :    38.9284
   Total  . . . . . . . . :    701.6 G
   Current unprotect used :     6128 M
   Maximum unprotect  . . :    14083 M

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. For the above example this would be (710 / 20.97) / 10 = 3.4%

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.

If currently growing, ensure the applicable temporary storage PTFs are applied.

If upon applying temporary storage PTFs the growth persists, iDoctor and / or DIRDUMP analysis may be required. For rapid temporary storage growth, you may be able to track down the offending job or task by observing storage allocation/deallocation using WRKSYSACT SEQ(*STGNET) .

Temporary Space PTFs
<Previous   Next>