We use to have problem with expiration hangs on v5, but haven't seen this on 
v6.  Will check out if expiration was running overnight or early this morning.

The REORG stuff.  Is there any way to know when TSm is performing unusual stuff 
on the db?  If this is occurring, I'm not seeing anything in the actlog to 
indicate this, but maybe it doesn't log anything.  


Thanks

Rick



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Billaudeau, Pierre
Sent: Wednesday, July 16, 2014 11:19 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM server appears to hang

Hi Rick,
        From my experience, I had problem with an Expire inventory process (was 
hanging on a very large node in term of items > 13 millions  )  that froze TSM 
but it was on 6.1 version. Also, REORG can use a lot of resources an impact TSM.

Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559

-----Message d'origine-----
De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De la part de 
Rhodes, Richard L.
Envoyé : 16 juillet 2014 11:08
À : ADSM-L AT VM.MARIST DOT EDU
Objet : [ADSM-L] TSM server appears to hang

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.

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


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.


-----------------------------------------
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.