Thanks Burak
.... and about the memory .... these 800MB is not amount needed by TSM, this
is TSM task startup parameter in MVS system .... simply we tried to increase
available memory amount with hopes to speed-up expiration. I'll try to
detect of bottleneck of this environment.

Thanks
Tom

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Burak Demircan
Sent: Thursday, August 08, 2002 10:44 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Expiration performance problem


I recommend to ugrade to latest maintenance level for your version 4.2.2.0
(Because 800MB of TSM usage is very very abnormal
One of my TSM servers work with 128MB RAM on AIX)
Second, you should do a unload / load db definitely. It will decrease your
utilization percentage
Regards,
Burak





        throuda AT HTD DOT CZ
        Sent by: ADSM-L AT VM.MARIST DOT EDU

        08.08.2002 11:04
        Please respond to ADSM-L

                        To:        ADSM-L AT VM.MARIST DOT EDU
                        cc:
                        Subject:        Expiration performance problem

Hi all,

Env: TSM server 4.2.0.0 on MVS 2.9
Database 20GB, 66% utilized, 8 volumes on HP512 (4x ESCON connected)

In last two months expiration process dramaticaly slowed down to approx
500-1000 objects/minute. Expipration of 100.000 objects takes 3-4 hours (no
other TSM processes runs at a time, TSM have about 800MB memory allocateed).
Compared to our other TSM environments it is very slow. DB grows from 10GB
to 20GB in last 2-3 months.

Any idea? Tune some parameters? Increase memory allocation? Or any ather
action like unload/load DB?


Any help will be appreciated.

Tom


=