Hi Zoltan,
Their is a couple of things I looking for every time I catch up a TSM v6 crash. 

1. See if Archive Log Space is not full

2. See the DB2Diag.log for more information

3. Boot up the TSM Server manually and see in the active console for more 
information.

Best Regards
Christian Svensson

Cell: +46-70-325 1577
E-mail: Christian.Svensson AT cristie DOT se
Skype: cristie.christian.svensson
Supported Platform for CPU2TSM:: 
http://www.cristie.se/cpu2tsm-supported-platforms

________________________________________
Från: Zoltan Forray/AC/VCU [zforray AT VCU DOT EDU]
Skickat: den 13 april 2010 20:20
Till: ADSM-L AT VM.MARIST DOT EDU
Ämne: Post Mortem on V6 server crash

My v6.1.3.3 server just rolled over and died for no apparent reason.  I
have it back up.

I am curios if there is some kind of audit or consistency checking I
should perform to make sure there aren't any broken-bits lying around that
I might need to glue back in place?

What do you usually do after a crash-and-burn?
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html