I have thought that if EXPIRE is stopped for any reason, when restarted, it
begins where it left off and goes to completion.  The next restart then
goes back to the beginning.


At 03:54 PM 5/30/2001 -0400, you wrote:

Thanks, but in my case it is shutting down when there is still a LOT of
things to expire.
When I restart it again, it starts up again and runs for hours.




-----Original Message-----
From: PINNI, BALANAND (SBCSI) [mailto:bp3965 AT SBC DOT COM]
Sent: Wednesday, May 30, 2001 3:32 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: EXPIRE INVENTORY shuts down
Importance: High


Wanda

If the no of objects are to to be inspected or inspected objects are
completed within time duration then it shuts off by itself.

In my case when I wanted to run for duration=10.
Then issued the cmd query proc I can see that as all objects get inspected
within the time it gets shuts off because
it has nothing else to inspect .PL do that again and see that how much time
it takes to inspect and expire.
This is what I saw in my case .It need not run all the duration in idle for
left out time.




-----Original Message-----
From: Prather, Wanda [mailto:Wanda.Prather AT JHUAPL DOT EDU]
Sent: Wednesday, May 30, 2001 12:16 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: EXPIRE INVENTORY shuts down


TSM 3.7.4 on AIX 4.3.3

I have EXPIRE INVENTORY scheduled to run for 1.5 hours in the wee hours:
EXPIRE INVENTORY QUIET=YES DURATION=90


Sometimes EXPIRE INVENTORY runs OK.
Other times it starts up, examines/expires 200-300 objects, then shuts
itself down again in 2-3 minutes with the normal message of SUCCESS.

Now I know it should be expiring 100,000+ objects per day.
If I start it again manually, it takes off and runs as you would expect.

Does anyone else see this happen?
Any idea what causes the premature shutdown?