Hello;

We're running ADSM V1 on an AIX server (3.2.5). The INVENTORY EXPIRATION
procedure is set to a 24 hr interval. This process takes 2-3 hours and is quite
a resource hog. In fact, it degrades the performance of our Sybase dataserver
quite substantially.

Since the time at which the EXPIRATION starts is based on the time that
the previous process completed makes it difficult to control. In order to
correct this I wrote a script that invokes the EXPIRATION process at a time
that I choose, in the hope that EXPIRATION INTERVAL option will then have no
effect on the timing of the process.

However, today I noted that an EXPIRATION process started 24 hrs after
yesterday's completed, despite the fact that the script forced an EXPIRATION
at 3AM last night. It seems that ADSM does see a scheduled EXPIRATION the same
as it sees a forced one.

Have I missed something here, or is there another solution?


Thanks in advance for any suggestions,

Ivan


Ivan Mews                               Technical Support
Global Travel Computer Services         Voice:  (905) 479-4949
7550 Birchmount Road                    Fax:    (905) 479-5420
Markham, Ontario, Canada                email:  ivan AT 
globetrl.global-travel.on DOT ca
L3R 6C6