Is anyone having/have had a problem getting the expiration process to run.  We
are running ADSM 2.1.09 on a MVS server.  We have a 16 gigabyte ADSM database
with 325 clients (os/2,Mac,SUN,AIX) I am not sure when the expiration process
last ran successfully.  According to IBM with our size of database it will take
between 75-125 HOURS to complete the expiration process!!!  Whenever expiration
runs it seems our ADSM performance suffers significantly.  (Migrations,
Backups), we also experience hangs that cause us to bounce ADSM on the server.
IBM has given us a TRACE to run but the degradation caused by that is more then
the expiration problem.  I hope I am not the only one with this problem?  Any
suggestions would be greatly appreciated!!  Thanks
Don.Ludwig AT ccmail.fingerhut DOT com