PROBLEM:  (CLD EVT102712l, QAR 65386)    (Patch ID: OSF440-016)
********
This patch fixes a problem in which an application using the X/Open Transport
Interface (XTI) and the DECnet/OSI transport provider is unable to disconnect
a rejected request.

The problem is that when the application issues a t_rcvdis call to disconnect
the rejected connection it receives a TOUTSTATE error, which indicates that
the call was made in the wrong order.

PROBLEM:  (QAR 62532,QAR 64248)    (Patch ID: OSF440-023)
********
This patch fixes a streams problem in libxti. The t_getprotaddr() function
will cause a memory core dump if either of its second or third argument is
NULL.
PROBLEM: (93806, FR_G04269, NL_G05189) (PATCH ID: OSF440-958)
********
Any threaded application that uses XTI/TLI could terminate or hang with an
internal mutex locked if t_snddis() is called while another thread is
receiving an event.  Typical application error messages may include
the following example from Visual Threads:
Error: programmingError.missingUnlock in libpthread.so
 Thread <xx>_<xx>@<some location> terminated while holding
 Mutex_<xx>@__init_xtilib.

or a typical kernel stack trace of the hung/block thread:

 thread_block()
 sleep_prim
 mpsleep
 osr_sleep
 osr_getmsg_subr
 osr_getmsg
 .
 .
 .
 _Xsyscall