On Feb 16, 2008, at 8:30 AM, Jeff White wrote:

14-02-2008 19:31:31      ANR8223W (Session: 877917, Origin:
COUXIPR05_STA)  Unable  to connect to remote system 172.20.34.21
due to
                          unexpected return code 67(SESSION: 877917)
====> Return code 67 = "EADDRINUSE"

That errno seems to be centric to this problem.  Its classic cause in
TCP/IP communications is that the local end has attempted to create a
socket, and then bind a specific port number to it - but some other
process is already using that port number.  That port number would be
one either specified in your options file or be a product default.
See http://www.redbooks.ibm.com/abstracts/TIPS0564.html for a
convenient summary of port specifications.  See the TSM manuals for
more detail.  You can use lsof, netstat, and like commands to see in-
use ports.

I would also check your hardware for anomalies.  Where you cannot
cancel a session or process, that usually indicates an I/O hang,
where a device has stopped responding and is blocking progress.
There should be site monitoring in place to call out device problems,
so they won't be the mystery cause of dependent software failing to
function.  At a minimum, check your AIX Error Log in conjunction with
involved TSM server Activity Logs.

   Richard Sims