ADSM-L

Re: High CPU and Not Responding

1998-01-20 11:24:52
Subject: Re: High CPU and Not Responding
From: Paul D Brown <pdbrown AT ASHLAND DOT COM>
Date: Tue, 20 Jan 1998 11:24:52 -0500
Thanks for your response, Tim.  The strange thing about this problem is
that if I cancel ADSM and restart it, the CPU
usage after the restart is back normal, and if I restart the EXPIRE it runs
fine with no high CPU usage.
Our practice has been to cancel ADSM as soon as it goes high CPU and
restart ADSM to get EXPIRE to finish.
This requires too much hands on for sure.
Thanks,
Paul
PDBrown AT Ashland DOT com
To:       ADSM-L AT VM.MARIST DOT EDU
cc:        (bcc: Paul D Brown)
From:     "Pittson, Timothy ,HiServ/NA" <tpittson AT HIMAIL.HCC DOT COM>
Date:     01/20/98 02:06:25 PM GMT
Subject:  Re: High CPU and Not Responding




I've noticed the same behavior from time to time on our ADSM server
running on AIX... this seems to happen during EXPIRE processing when
ADSM is processing one of the larger client nodes (1 million+ files).
The server does eventually respond, sometimes after 10+ minutes.
Tim Pittson
tpittson AT hiserv-na DOT com
>-----Original Message-----
>From:  Paul D Brown [SMTP:pdbrown AT ASHLAND DOT COM]
>Sent:  Tuesday, January 20, 1998 8:28 AM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Re: High CPU and Not Responding
>
>Jerry,  My data base is 1,980 MB and the MVS processor is not running 100%
>at the time I run the EXPIRE.
>I run the EXPIRE daily, while no backups are running.  I also turn
>migration off during this time by setting reclaim to 100%.
>In other words nothing is running except EXPIRE during the hang ups.  The
>MVS system is normally running in the 80% range
>during this time.  I also have the same problem Saturday and Sunday.
>Thanks for the reply.
>Paul
>To:       ADSM-L AT VM.MARIST DOT EDU
>cc:        (bcc: Paul D Brown)
>From:     Jerry Lawson <jlawson AT THEHARTFORD DOT COM>
>Date:     01/20/98 12:02:27 AM GMT
>Subject:  High CPU and Not Responding
>
>
>
>
>---------------------------- Forwarded with Changes
>---------------------------
>From: INTERNET.OWNERAD at SNADGATE
>Date: 1/19/98 12:22PM
>To: Jerry Lawson at ASUPO
>*To: *ADSM-L at SNADGATE
>Subject: High CPU and Not Responding
>--------------------------------------------------------------------------
-
>----
>----
>Paul -
>A couple of questions for you in response.....
>1.  What is the level of other activity on your MVS system?  Are you now
>running flat out?
>2.  How big is your DB?
>We had a similar high level of activity, although I don't recall it got so
>bad that we couldn't enter commands, though.  The performance guy was
>concerned about the high level of CPU activity, though.   While we ran
>Expire
>at night, we had to delay other processing, such as Backup storage pools
>and
>migrations into times when other MVS tasks could have used the extra CPU.
>We
>ultimately changed the Expire inventory to run on Saturday, and have been
>very pleased with the results.
>Jerry Lawson
>jlawson AT thehartford DOT com
>
>______________________________ Forward Header
>__________________________________
>Subject: High CPU and Not Responding
>Author:  INTERNET.OWNERAD at SNADGATE
>Date:    1/19/98 12:22 PM
>
>Questions for you ADSMers,
>       I am running ADSM Server  release 2 1.0.12 on MVS  OS/390.
>And I am having the problem each day when the EXPIRE runs, the ADSM STC
>goes into high CPU usage and will not respond to commands.
>I had this problem once before about a year ago and the problem was having
>a large VOLUME HISTORY file.
>The Volume History file is very trim today with only seven days worth of
>activity.
>Any body have any other like occurrences?
>Thanks,
>Paul Brown
>Ashland Inc.
>Lexington, Ky
>PDBrown AT Ashland DOT com
<Prev in Thread] Current Thread [Next in Thread>