Could you elaborate a bit futher on the problems encountered with
TCP/IP 3.2? We are running ADSM for MVS (2.1.0.10) and TCP/IP 3.2. We
have encountered some problems with restores on NT, AIX and OS2
systems. However restoring to Solaris works fine.  We have a workaround
to the NT restore problem but haven't tried it for the OS2 or AIX systems yet.
The problem we were seeing was that restore session  would just stop
after a while, a query of the  session  would show it in a IDLEWAIT.
Ultimately it would time out after the  IDLETIMEOUT was invoked,
however the error message would state that it was a TCP/IP failure. Our
workaround was to have a ADSM trace running on the client and the
server. This was discovered by accident when we were collecting trace
data  while investigating a different problem.
FYI the main reason we went TCP/IP 3.2 from 3.1 was performance
related. We upgraded after IBM convinced us that we would experience a
hugh improvement in performance for backup. They were right.
Regards
Laurie de Mamiel
Woodside Offshore Petroleum