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