|
THAT is a good question James. Unless it was logging some other problem (check problem log - maybe taking dumps or something ?). And that IS weird that there would be NO messages in QSYSOPR. Do you have QSYSMSG set up ? Any job/jobs on the IBM scheduler that could have gone wacky ? Chuck -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H H Lampert Sent: Friday, April 22, 2005 1:21 PM To: Midrange Systems Technical Discussion Subject: Re: Our 200 has developed a weird lockup problem (SRC B600 0615) > B6000219 and B6000615 that indicate that a system does > not have enough auxiliary (disk) storage to continue > processing." Fascinating. Now that at least two of you, and the doc I was linked to, mention it, there was a "Serious storage condition" (but no "critical storage condition) message in the QSYSOPR *MSGQ. How does an almost entirely idle box develop a serious storage condition that escalates to critical in a matter of minutes? And how do I keep it from crashing before I can locate and excise the space-hog? Any ideas? -- JHHL
As an Amazon Associate we earn from qualifying purchases.
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.