The EXPIRE process finally finished about 6 hours after starting. It reported
as successful but was qualified with "finished before completion" due to being
cancelled.
I got some info from IBM via the PMR.
1: CAN PRO <number> and CANCEL EXPIRATION accomplish the same thing. CAN PRO
requires the process number, but CANCEL EXPIRATION cancels any currently
running EXPIRE process. CANCEL EXPIRATION was created so it could be used in
scripting where the process number would be unknown. Similar to the CANCEL
REPLICATION command.
2: the EXPIRE process works on a filespace-by-filespace basis for a node.
It processes ALL of given filespace, then checks for duration limit. If below
the duration limit, it moves on to the next filespace. If beyond duration, the
process stops.
It's unknown why it took 6 hours to process a single filespace, the typical
time on this server is about 1 hour.
So, something odd, hopefully won't see that again. It really messed up my
maintenance processing with significant that delay.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Michael malitz
Sent: Wednesday, May 06, 2015 10:17 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] AW: EXPIRE INVENTORY problem
Hallo Harold,
you should use the command "cancel expiration" instead of "cancel process".
With cancel expiration you have "checkpointing" at transaction boundaries.
Rgds Michael Malitz
-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag
von Rick Harderwijk
Gesendet: Mittwoch, 6. Mai 2015 16:44
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: EXPIRE INVENTORY problem
If you cancel an expiration, does it not log every transaction, so that when
you cancel, it effectively does a rollback on all the entries in the database?
That might take some time as well...
On Wed, May 6, 2015 at 4:31 PM, Vandeventer, Harold [OITS] < Harold.Vandeventer
AT ks DOT gov> wrote:
> I'm running TSM 6.3.4.300 on Windows.
>
> I have a script that issues EXPIRE INVENTORY DURATION=90 RESOURCE=40
> WAIT=YES.
>
> It was still running over 2 hours after start.
>
> I issued a CANCEL PRO and it's been in "cancel in progress" for over
> 30 minutes.
>
> During all this time, Q PRO is reporting a constant number of nodes
> processed, objects examined and objects deleted.
>
> Database and log space look fine, Health Monitor via the AdminCenter
> GUI looks fine.
>
> What's happening in that process that would cause this behavior?
>
> ------------------------------------------------------------
> Harold Vandeventer
> Systems Programmer
> State of Kansas - Office of Information Technology Services STE 751-S
> 910 SW Jackson
> (785) 296-0631
>
>
> [Confidentiality notice:]
> **********************************************************************
> * This e-mail message, including attachments, if any, is intended for
> the person or entity to which it is addressed and may contain
> confidential or privileged information. Any unauthorized review, use,
> or disclosure is prohibited. If you are not the intended recipient,
> please contact the sender and destroy the original message, including
> all copies, Thank you.
> **********************************************************************
> *
>
|