CPU at 100%

[Jim Langston <jlangston@xxxxxxxxxxxxxxxx>]

9406-500 V3R7M0

Yesterday around 2:30 our system did something unexpected.
Our system stopped responding to requests, and looking at the
CPU indicator, it was at 100%  Within about 25 minutes I got
one response on my session, then it "locked up" again.  I could
not get anywhere to find out what was going on, I couldn't even
log onto the console, as it normally logs onto QINTER unless
we ENDSBS *ALL *IMMED then it switches to QCTL.

I wound up IPLing and waiting and hour and forty five minutes for
it to re-IPL after and ABEND.  So, a few questions:

1. How do I find out what actually happened?  I did a DSPLOG and
   found nothing out of the ordinary.  I searched for RUNPTY in the
   last of the job logs in QEZJOBLOG but didn't find it (I thought
   someone may have switched their job priority to 1).

2. How do I get my console to always log on to QCTL instead of
   QINTER at a high run priority so I can actually get in and find out
   what is wrong before I ABEND the system?

3. Anything I should be doing to prevent this?  Not that I know what
   "This" is.

TIA for any suggestions.

Regards,

Jim Langston

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---