Re: Who has a big QTEMP?

[Jim Langston <jlangston@xxxxxxxxxxxxxxxx>]

Well, I think an easy way to find out what is taking up the QTEMP space is to 
start
ending the subsystems.  After each subsystem is ended, do a WRKSYSSTS and look
at the DASD usage.  When the DASD usage drops down that would be the subsystem
the job is in.

If you end all the subsystems and the DASD usage is still there it would by 
necessity
be an OS/400 issue.

Regards,

Jim Langston

Date: Fri, 25 Aug 2000 15:13:11 -0400
From: "Ingram, Terry (USE)" <Terry.Ingram@uescape.com>
Subject: Who has a big QTEMP?

We ran a disk RTVDSKINF and noticed 17% (about 50G) is being tied up in
"temporary space" as referred to on the PRTDSKINF.  In an IBM manual it said
this is due to objects in QTEMP.

What made me look at the PRTDSKINF is that we were at 92% ASP use.  We IPL'd
and it went down to 67%.  After 3 weeks, we are up to 87%.

The big question is, which of these jobs has the big QTEMP?  I'm wondering
if we can bounce a subsystem, better yet end and restart a job instead of
IPL'ing to get the space back.

TIA

+---
| 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
+---