OS/390 R5 APAR OW37908 reports ADSM client hang conditions.  This problem
was discovered a few
months ago.  Check if the corresponding PTF is applied on your system.   In
addition to the OS/390 R5
APAR you should apply ADSM PTF UQ28274 which brings your server up to level
3.1.2.20 where a
potential hang condition (variant of PQ21945) while running on OS/390 R5
TCP/IP has been corrected.
Thanks, Bob La Brie ADSM Development


"Louis J. Wiesemann" <ljwies01 AT LOUISVILLE DOT EDU> on 04/15/99 08:31:48 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Bob La Brie/Tucson/IBM)
Subject:  ADSM Connection Problem





   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