• Subject: Re: CPU at 100%
  • From: Chuck Lewis <clewis@xxxxxxxxxx>
  • Date: Tue, 25 Jan 2000 12:09:27 +0000

Jim,

You can DEFINITELY do what Mark suggests and I have done that but that does NOT
guarantee that you will be able to do anything. Sometimes yes, sometimes no. We
had this happen several years back and could get NOTHING out of the console 
after
keying in one command and pressing Enter. This was on a 530 running V3R7 with 
500
users. I called IBM and we did a dump. They found that is was a problem in a 
call
in a BPCS program...

Chuck

Mark Allen wrote:

> Put a Work station entry with the name of your "console" in the QCTL
> subsystem
>
> Mark Allen
> IS Manager
> Kelly's Kids
> markallen@kellyskids.com
>
> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Jim Langston
> Sent: Tuesday, January 25, 2000 10:06 AM
> To: 'MIDRANGE-L@midrange.com'
> Subject: CPU at 100%
>
> 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
> +---
>
> +---
> | 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
> +---

+---
| 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
+---

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].