I wouldn't say expiration running over 24 hours a cause for alarm per say.
I have seen expiration running over 10 days.  This occurred when TSM server
was upgraded to address expiration issue with Windows system objects.  Few
years back.

That being said, I would examine past actlog to see if any irregular anr
messages appears during expiration to see if  abnormality is spotted.

Sung Y. Lee

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/02/2006
02:01:44 PM:

> To Whom It May Concern:
>
> Expiration ran over 24 hours yesterday. I cancelled it when the DB
> backup job started. We recently migrated 30-40 volumes from an old
> sequential pool that became went into pending. About 30 volumes passed
> the re-use delay period and went to scratch 2 days ago. I was wondering
> if this could have the cause of an extended expiration job.
>
> Any thoughts would be appreciated.
>
>
> George Hughes
>
> Senior UNIX Engineer
>
> Children's National Medical Center
>
> 12211 Plum Orchard Dr.
>
> Silver Spring, MD 20904
>
> (301) 572-3693
>
>
> Confidentiality Notice: This e-mail message, including any attachments,
is
> for the sole use of the intended recipient(s) and may contain
confidential
> and privileged information.  Any unauthorized review, use, disclosure or
> distribution is prohibited.  If you are not the intended recipient,
please
> contact the sender by reply e-mail and destroy all copies of the
> original message.
>