I have come across the same problem with ADSM Server for MVS V1, but
found out that it is fixed in V2.  I have tested this and found this to
be true (i.e. ADSM reconnects to TCPIP under V2 of ADSM for MVS)

Dianne Sharp
Operations Analyst
Clear Communications, Auckland, New Zealand

>----------
>From:  Pittson, Timothy ,HiServ/NA[SMTP:tpittson AT HIMAIL.HCC DOT COM]
>Sent:  Monday, 12 May, 1997 12:16PM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Re: TCPIP outage, ADSM recycle?
>
>Julie,
>        ADSM is supposed to reconnect when TCPIP comes back up but sometimes,
>as you've just discovered, it doesn't.  After getting burned a couple of
>times, I had ADSM recycled whenever TCPIP was bounced.
>
>Tim Pittson
>tpittson AT himail.hcc DOT com
>
>>----------
>>From:  Julie Phinney[SMTP:julphinn AT EMPHESYS.E-MAIL DOT COM]
>>Sent:  Sunday, May 11, 1997 6:11 PM
>>To:    ADSM-L AT VM.MARIST DOT EDU
>>Subject:       TCPIP outage, ADSM recycle?
>>
>>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
>>
>