RE: CPU at 100% -- MIDRANGE-L

You should have used ENDJOBABN  End Job Abnormal, works faster 

____________________Reply Separator____________________
Subject:    Re: CPU at 100%
Author: "Jim Langston" [SMTP:jlangston@conexfreight.com]
Date:       01/25/1900 6:01 PM

We have 17g of HD in one ASP and only 68.55% of it used,
so I'm fairly sure it's not DASD (unless there was a killer program
that ate up temporary space).

No one was running anything out of the ordinary that I am aware
of, as normally I am the only one who does the off the wall things,
such as running queries, update programs, etc...  Everything was
just SOP as far as I'm aware.

That's what's so puzzling.  This happened once before but I knew
exactly what it was that caused it last time.  I was waiting for everyone
to get off the system so I could end it, but one person was running
a long winded batch.  So I changed the run priority of that batch to
1 and it did the exact same thing.  Locked up everyone until the
batch finished.  Which actually wasn't that bad, since that's what
we were waiting for anyway.

Regards,

Jim Langston

"Stone, Brad V (TC)" wrote:

> Are you running low on disk space?  Was someone running a killer query?
Was
> someone restoring a very large file/library?  SQL?  Showcase?  Any query
> product that builds temp files can do this, and if you're low on disk,
that
> will not help.
>
> Brad
>
> > -----Original Message-----
> > From: Jim Langston [mailto:jlangston@conexfreight.com]
> > 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 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
+---