While the data collection could be contributory, I highly doubt it was
causal. Since you use TOMCAT and other Java based tooling I'm guessing a
JVM got whacked up somehow? Depending on what the damaged objects were, I
would concentrate on those. Unless it happens again, I'd let it go.
Chief Technical Architect
Agile Technology Architects
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Tuesday, April 22, 2014 12:01 PM
To: Midrange Systems Technical Discussion
Subject: Re: Help! System has become unresponsive!
On 4/21/14 1:11 PM, Jim Oberholtzer wrote:
Do yourself a favor and immediately run reclaim storage and then IPL.
You can wait for this weekend but I'm guessing you'll see some damaged
objects along the way.
Not quite immediately, but I did a RCLSTG. I brought the subsystems down
right around 5 yesterday evening, and it was ready to re-IPL by 6. A bunch
of damaged objects turned up, thankfully none of them appeared to be
permanent user objects.
We'd had a power failure one night, late last week, that might have left a
ticking time bomb in the system.
The most suspicious thing, to my eye at least, though, was a CPF0A9B from a
Message . . . . : Probe failed for category QHTTP.
Cause . . . . . : The probe that collects data for category QHTTP data
failed. The collector will stop data collection for this category.
Recovery . . . : Refer to the job log for more details about the
Start data collection for this category to try data collection again.
It happened at least 15-20 minutes after the system became unresponsive,
right about the time I first screamed for help yesterday.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l