% temp addresses = 96.800

[D.BALE@xxxxxxxxxxxxx]

Well, it appears that David's warning about the archives has reached reality;
I am unable to get to the archive site.  Whoops... well I am on, but it is
running VEEEEEERRY slow, am getting "no response" messages (other web sites
are responding quickly, FYI).

Seeing the message "Nearly all available machine addresses used." (CPI0997) in
the QSYSOPR message queue, I am currently looking at a WRKSYSSTS screen on our
9406-D60 (running V3R2):

% CPU used . . . . . . . :       43.3    System ASP . . . . . . . :    17418 M
Elapsed time . . . . . . :   00:00:00    % system ASP used  . . . :    67.4334
Jobs in system . . . . . :        452    Total aux stg  . . . . . :    17418 M
% perm addresses . . . . :     18.814    Current unprotect used . :      849 M
% temp addresses . . . . :     96.800    Maximum unprotect  . . . :     1046 M

The second level text for the message recommends that we "Do an initial
program load (IPL) to make more addresses available to the system.  The IPL
will automatically release available addresses to the system."

We rarely IPL this box (or any of our boxes for that matter), only once in the
6 months I've been here.

The archives finally popped up results for my query and I found Neil Palmer's
post from August 1997 about SF42563; that PTF is "Temporarily applied" on our
box.

So, I guess we'll do an IPL this evening.  Can anybody tell me what causes the
temp addresses to get this high?  BTW, I understand that this problem goes
away with RISC, and we are close to upgrading to new boxes.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---