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

Other things:

Once it's up, run a RCLSTG and clear the QRCL lib.  At a former employer
we had an old D02 or D20 test box that wasn't used for much of anything.
It ran out of disk at one point.  Running the RCLSTG freed up 74% by
deleting over 10K objects.

GO CLEANUP and run immediately.  This should eliminate old qhst files
among other things.

Look for journal receivers & delete if not needed.  Ditto for save
files.

Set that TR adapter to not go online at IPL to eliminate messages from
it.


John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787  F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: Ingvaldson, Scott [mailto:SIngvaldson@xxxxxxxxxxxx] 
Sent: Friday, April 22, 2005 2:33 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Our 200 has developed a weird lockup problem (SRC B600
0615)

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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.




This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in the future then please respond to the sender to this effect.