Re:CPU at 100%

It is amazing how many people have their printer files changed 
to *nomax on the number of output records.  I know of a local 
company that had a large AS/400 die of the same death.

Also, all of the people who change their joblogs to *wrap instead 
of finding out why they have an infinite loop in the first place.

We changed all of our group profiles to have a maximum dasd instead 
of *nomax.  Wrote a program that sends an email every morning with 
their percent full.  We did this to stop the runaway query.  Which 
killed our largest 400, outside of development ;-)  





ESundell@pmi.delta.org on 01/25/2000 03:26:28 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        Re:CPU at 100%

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

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.

____________________Reply Separator____________________

We had our F70 do this twice, the first time a RPG program went nusts and
started to produce a report in QSPL, it bombed before it finished so it left
a
huge member in QSPL but no output, the second time a new guy ran a query off
all
of our bigest files and dumped it to a new file. Both of these had no real
warnings in DSPLOG and I found them with a little program that I wrote to
find
the largest objects on the system, here it is if you need it:

PGM                                                       
                                                          
CHGJOB     LOG(4 00 *SECLVL) LOGCLPGM(*YES)               
                                                          
DSPOBJD    OBJ(*ALL/*ALL) OBJTYPE(*FILE *OUTQ *MSGQ) +    
             DETAIL(*FULL) OUTPUT(*OUTFILE) +             
             OUTFILE(MYLIB/OBJSIZE) OUTMBR(*FIRST *REPLACE)
                                                          
RUNQRY     QRY(MYLIB/QRYOBJSIZE)                           
           QRYFILE((MYLIB/OBJSIZE))                       +
           OUTTYPE(*PRINTER)                              
                                                          
                                                          
ENDPGM                                                    


        And The Query:

        Selected files

     
  ID     File           Library       Member        Record Format

  T01    OBJSIZE        MYLIB         *FIRST        QLIDOBJD

Select record tests

  AND/OR   Field             Test     Value (Field, Numbers, or
'Characters') 
           ODOBSZ            GE       1000000

Ordering of selected fields

  Field           Sort      Ascending/  Break  Field

  Name            Priority  Descending  Level  Text

  ODLBNM          10        A           1      Library

  ODOBNM          40        A                  Object

  ODOBTP          20        A                  Object type

  ODOBAT                                       Object attribute

  ODOBSZ          30        D                  Object size

  ODOBTX                                       Text description


Report column formatting and summary functions

  Summary functions:  1-Total, 2-Average, 3-Minimum, 4-Maximum, 5-Count

  Field           Summary    Column                                Dec  Null

  Name            Functions  Spacing  Column Headings         Len  Pos  Cap

  ODLBNM                     4        LIBRARY                  10

                                       NAME

  ODOBNM                     4        OBJECT                   10

                                       NAME

  ODOBTP                     4        Object                    8

                                      Type

  ODOBAT                     4         OBJECT                  10

                                      ATTRIBUTE

  ODOBSZ          1          4        OBJECT                   10    0

                                       SIZE

  ODOBTX                     4                                 50

                                      DESCRIPTION

You can format it with what you want, works good for cleanup too,hope it
helps,
good luck

Eric
"It's a little known fact that the Dark Ages were caused by unresolved Y1K
issues."
+---
| 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
+---