Hi,
In my case expiration is not set node specific. We have set administrative schedule with expiration time to 120minutes. I am having TSM 6.4 database in which we have found major issue with DB2 permission level issue which brought in to notice by sr. Tivoli expert. He discovered that
1 TSM server service is running with ID which is having ADS authentication.
2 TSM DB2 database is running with the windows local system authentication.
He is recommended to use single id either locally created on windows server level or domain power user id which is not bind with any security restrictions. So we have done following
1 created local id at windows level & added the same in local ADMINISTRATOR,DBUSERS & DBADMINS groups.
2 Open DB2 Control center & logged in with ID authorized to login & checked the permissions. Later added the local id created with required permissions to act as db admin & security admin permissions.
3 In Services.msc changed the TSM server service authentication assigned to newly created id.
4 Restarted the server at OS level & monitored the DB2 & TSM server service which is found running.
This solution is given in below link provided by IBM.
http://www-01.ibm.com/support/docview.wss?uid=swg21445245
Now we have stopped the administration schedule now & found the automatic expiration is running with duration of 24 hours which is default mentioned in server opt file. Now it shows all 33 nodes with large amount of files expired.