× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: CPU at 100%
  • From: "Shaw, David" <dshaw@xxxxxxxxxxx>
  • Date: Tue, 25 Jan 2000 11:45:36 -0500

-----Original Message-----
From: Jim Langston [mailto:jlangston@conexfreight.com]

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.

+---

Jim,

1)  One option: Is PM/400 running on your system?  If it is, you should be able
to find it this way:

        a) GO QMPGLIB/PM400
        b) Take Option 2, "Work with Historical Active Jobs"
        c) For Member, choose *SELECT, and for List tasks, *YES - then press
Enter
        d) Pick the member that was being used when your system went belly up
        e) It should display data from the last collected interval before you
IPL'ed - position the cursor over CPU% and press F16 to sort.  It should show
you the job or task that was eating your machine.

2)  If your QCTL subsystem still has the default workstation type entry of *CONS
set to "Control job at *SIGNON", just change system value QCONSOLE to the name
of your console device, for example DSP01.  If you have a workstation name entry
in QINTER for your console, you should either delete it or change it to "Control
job at *ENTER".

3)  Leave the machine turned off? <grin>  Seriously, it's hard to say until
"this" is identified.

I hope this message is helpful, at least a little.

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.