Finding reason for high temp storage maximum -- MIDRANGE-L

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

Subject: Finding reason for high temp storage maximum
From: oliver.wenzel@xxxxxxxxxxxxxxxxxxxxxxx
Date: Thu, 4 Dec 2003 09:44:01 +0100
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Hiya,

on our 820 the wrksyssts shows a very high temp storage maximum number: 
35247M.  Current temp storage is at 5921M.

The 35GB would have put as close to the danger line at 90% DASD. Any 
chance to find out now which job has used up so
much temp storage?

Regards,

Oliver

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Finding reason for high temp storage maximum , Bryan Dietz
Re: Finding reason for high temp storage maximum , Larry Bolhuis
Re: Finding reason for high temp storage maximum , Martin Rowe

This mailing list archive is Copyright 1997-2024 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.