Re: ADSM Connection Problem
1999-04-16 10:07:49
We had the same problem when I believe we were at ADSM 3.1.1.13. It happened
as soon as we upgraded to the Open Edition of OS/390 V2.5.
I'd have to check with my co-workers but I believe we applied a TCP/IP and
MVS fix as well as upgrading to 3.1.1.15. Since then we've only had one
hang.. which is a lot better than before. Previous to this it would hang
every other day.
Good Luck. I know only too well how irritating this problem was, not to
mention how difficult it is to get a fix.
As I recall we had no way of determing when the problem occurred as no error
message was given out by ADSM or MVS. IBM felt the problem was TCP/IP
related and their only answer was to run a TCP/IP trace as soon as the fault
was detected... better act quick too as a TCP/IP trace in most cases will
wrap around in 5mins.
Nathan
-----Original Message-----
From: Francis Maes [SMTP:fr.maes AT CGER DOT BE]
Sent: Friday, April 16, 1999 6:16 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: ADSM Connection Problem
Hello Louis,
We have the same kind of problems with ADSM 3.1.2.14 on OS/390 2.4.
We have opened a PMR. It seems the "new" version of the Expire
Inventory is
locking or hanging the other functions.
We have had the same problem: no way to execute admin commands. Stop
and
restart server to resolve the problem.
IBM will ask you to install 3.1.2.20. I don't know if this level
will
resolve this kind of problem.
Regards,
Francis.
-----Message d'origine-----
De : Louis J. Wiesemann <ljwies01 AT LOUISVILLE DOT EDU>
À : ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
Date : jeudi 15 avr. 1999 21:36
Objet : 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
>
|
|
|