RE: Our 200 has developed a weird lockup problem (SRC B600 0615)

["Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx>]

Sorry, my apologies for over-simplifying things...  If it won't IPL at
all, the only way I know is a manual IPL with the clear, clear, clear at
IPL options.  Of course you'll lose all of your spooled files and
joblogs doing this....  Then once the system is up in a restricted state
do some cleanup.  One thing that I found that caused big problems on our
test system was a trace that SupportLine had asked me to run, then I
forgot about it and it ran for months.

Regards,
 
Scott Ingvaldson
iSeries System Administrator
GuideOne Insurance Group

-----Original Message-----
date: Fri, 22 Apr 2005 11:21:03 -0700
from: "James H H Lampert" <jamesl@xxxxxxxxxxx>
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