Hi Louis,

Yes, it happened to us once before and we had to bring the ADSM server
down an up again to have access back.  Confirming your investigation, no
indication to what could have caused it we found.  My suspicion was one
of the running administrative client session opened for our computer
room operators to check on ADSM activities. At that time the running
operator administrative client session/window could access the server
but no other administrative client window could be run from anywhere on
the network.  If it happens to you again, try to look for a running
administrative client session first and kill it . See if access to the
server could be established again this way without recycling the ADSM
server.

Note: We are running ADSM 3.1.1.0 on a RS/6000 R50

Regards,
Wassim

"Louis J. Wiesemann" wrote:

>    We are running ADSM 3.1.2.1 on OS/390 2.5.  Today we experienced
> a problem we have not seen before.  The server was still running and
> appeared to be processing normally.  It was doing reclaimations and
> processing tape mounts.  It would process commands sent to it via
> the MVS console with normal responsiveness.
>
>    But we could not connect to it over the network.  Attempts by
> clients to connect to it would hang.  We verified that TCPIP was
> still functioning properly.  We could TELNET, PING, etc. to the
> MVS server.  We just could not access ADSM.  Sessions already
> accessing ADSM at this time were also hung.
>
>    We had to cycle the server to get access back.  I reviewed the
> activity log for the time of the failure, but did not find any
> errors that seemed related to the problem.
>
>    Has anybody else seen a problem like this or have any ideas
> about what else to check?  We did take a dump before cycling the
> server.
>
>    Thanks for any help with this.
>
> _______________________________________________________________
> Louis J. Wiesemann            University of Louisville - IT/DCS
> Phone: (502) 852-8952
> Email: LJWIES01 AT LOUISVILLE DOT EDU