Thanks for the info. We're stuck on v6.2.5 for a while. We have a library sharing environment, and a single v5 instance is pinning our v6 servers at v6.2.5. Once that instance is upgraded we will push up to v6.4.
We rebooted this tsm/aix yesterday afternoon and so far we haven't seen any reoccurrence of the hangs. Rick -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Mitchell, Ruth Slovik Sent: Wednesday, July 16, 2014 3:25 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM server appears to hang Rick, Here's a handy technote you might want to keep in your back pocket if these do turn out to be DB2 related: http://www-01.ibm.com/support/docview.wss?uid=swg21452146 , (be sure to refresh it occasionally since it's been getting updated lately). If you do turn up reorg-related issues, you might want to consider upgrading the server version if feasible. Reorganization has been optimized substantially since 6.2.5. There are also three TLS/SSL vulnerabilities in this version, announced on May 8, 2014, and in APAR IT01590: http://www-01.ibm.com/support/docview.wss?uid=swg1IT01590. We found the upgrade from 6.2.5 to 6.3.4.xxx to be painless. Ruth -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rhodes, Richard L. Sent: Wednesday, July 16, 2014 12:41 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM server appears to hang We will be looking at all these things. Right now we did the normal shutdown/reboot just to be sure (not sure of what!). 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.
