Hello,

we also had 45 min of expire processing. Since installation of the MVS
server V3.1, this elapsed time reduced to 10 min.!

Regards, rl

> -----Original Message-----
> From: Laurie De Mamiel [SMTP:Laurie.L.R.DeMamiel AT WOODSIDE.COM DOT AU]
> Sent: Tuesday, January 20, 1998 2:38 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: High CPU and Not Responding
>
> We have had similiar experiences, but not because of an EXPIRE
> running.
> We have seen very slow response to commands, in the order of minutes,
> sometimes greater than 5 mins. This has happened when we have a large
> amount of activity with adsm, ie a number of backups starting together
> and a couple of migrations running Though I must admit if we ran an
> EXPIRE it would only make things worse.
>  Our problem is exacerbated by the fact that our system has very
> relatively small cpus. We are running ADSM 2.1.0.13 on MVS on a
> 9672-r41. ADSM is not able to take advantage of the other cpus, thus
> we
> see a severe cpu bottleneck at peak times.
>
> Regards
> Laurie de Mamiel
> Woodside Offshore Pet.
> ----------
> From: ADSM-L /  , ADSM-L AT VM.MARIST DOT EDU; pdbrown /  ,
> pdbrown AT ASHLAND DOT COM
> To: ADSM-L /  , ADSM-L AT VM.MARIST DOT EDU
> Subject: High CPU and Not Responding
> Date: Tuesday, January 20, 1998 12:09AM
>
> 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