"Serious storage condition may exist" -- MIDRANGE-L

Subject: "Serious storage condition may exist"
From: "James H H Lampert" <jamesl@xxxxxxxxxxx>
Date: Thu, 11 Nov 2004 08:35:00 -0800 (PST)
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>

We've suddenly started getting "serious storage" and "critical storage"
QSYSOPR messages on our production box, and so far, we're unable to
determine the cause. We've got very few spool files, and very little in
QRPLOBJ. Any other suggestions on where to look?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: "Serious storage condition may exist" , Al Barsa
RE: "Serious storage condition may exist" , Elvis Budimlic
RE: "Serious storage condition may exist" , Jeff Crosby
Re: "Serious storage condition may exist" , Jim Franz
RE: "Serious storage condition may exist" , Joe Pluta
Re: "Serious storage condition may exist" , John Candidi
Re: "Serious storage condition may exist" , Kat Kruse
Re: "Serious storage condition may exist" , Kyle Collie
Re: "Serious storage condition may exist" , pnelson

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