Hello, 
seems like I have been facing the same experience with one of my TSM 
server (v.6.2.5).  I have been quite lucky until now because the server 
has recovered on its own. I opened a case  in this matter with support a 
few month ago. I was told to focus on setting a time window for reorg 
activity. 
Their recommendation: 
"Please find the day of time when the server is not under a heavy 
workload, if some processes are running it is not a problem. Avoid the 
time period expire or reclamation."
I haven’t  done it, yet. The server in question is busy all day long every 
day.
Josef




Od:     "Rhodes, Richard L." <rrhodes AT FIRSTENERGYCORP DOT COM>
Komu:   ADSM-L AT VM.MARIST DOT EDU
Datum:  16.07.2014 17:08
Předmět:        [ADSM-L] TSM server appears to hang
Odeslal:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



Hi Everyone,

The past couple of days we're had a strange problem with one of our TSM 
instances (v6.2.5).  At times it appears to hang.

Last night (and the previous night) it had many servers that got a dozen 
or more sessions.  This is really strange!  This morning as I was looking 
at this, cmds like "q vol" and "q stgpool" hang - no response!  Commands 
like "q node" and "q proc" work.  The server was doing very little I/O. 
All of a sudden the hung cmds all ran through and the server I/O jumped to 
200-400MB/s.  Something was locking I/O.  I think the many sessions are 
clients that retry because the server is not responding.

In the TSM actlog there are no unusual messages about the time it 
un-stuck.  The only strange entry in the actlog is a ANR9999D with 
lockwait error early the previous evening.    There are no AIX errors.

Any thought?

Rick






-----------------------------------------

The information contained in this message is intended only for the 
personal and confidential use of the recipient(s) named above. If the 
reader of this message is not the intended recipient or an agent 
responsible for delivering it to the intended recipient, you are hereby 
notified that you have received this document in error and that any 
review, dissemination, distribution, or copying of this message is 
strictly prohibited. If you have received this communication in error, 
please notify us immediately, and delete the original message.