Last night we had a regularly scheduled TCP/IP (3.1.0, on MVS) outage.
We have 2 ADSM started tasks (both 2.1.9), one uses TCPPort 1500,
one uses TCPPort 1501.  After the outage, the task using port 1501
had no trouble, as normal for both. But the task which uses 1500
registered no more session activity in the activity log.  No errors.
We do not cycle the ADSM servers when we have this normal TCPIP
outage.  This afternoon I tried to initiate a session with ADSM
and got a TCPIP connection failure.  I did a Q SESS and saw 6 sessions
which had been sitting for 18 hours.  We cycled ADSM and all appears
to be fine now, I can connect.  At these levels of ADSM and TCP/IP,
do we need to cycle ADSM when TCP/IP goes down?  We haven't had to
previously, and versions haven't changed..  Does anyone know?
Thanks!
Julie Phinney
JULPHINN @ EMPHESYS.E-MAIL.COM