ADSM-L

Re: Hung Server

1998-04-22 11:33:12
Subject: Re: Hung Server
From: "Smith, Richard" <smithrr AT MARITZ DOT COM>
Date: Wed, 22 Apr 1998 10:33:12 -0500
Bob,

        No, we have not upgraded yet.

Rick Smith
Maritz, Inc.
Storage & Security Administration
smithrr AT maritz DOT com
(314) 827-1584

> ----------
> From:         Bob La Brie[SMTP:labrie AT US.IBM DOT COM]
> Sent:         Wednesday, April 22, 1998 9:28 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Hung Server
>
> Rick,  Have you applied  PTF service UQ16502 etc. to bring ADSM upto
> 3.1.0.2.
> This is the latest ADSM
>                server for MVS and is now available via  PTF.?...I see
> you
> indicated V3 R1.
>                 We recently discovered a problem where certain threads
> can get
> hung when ADSM attempts
>                 to synchornize 2 threads.  PQ14970 addresses this
> problem and I
> have a fix test currently
>                 waiting to be verified on ADSM V2.
>                 This APAR is targeted to be included with the next PTF
> service
> level along with the
>                  reclamation utilities.  If it happens again take a
> comm dump
> with SDATA=(CSA,RGN,LSQA),
>                  open PMR and put the dump on testcase or index FTP
> server.
>                   If you can enter commands from the MVS console while
> it's
> hung  issue SHOW THREADS...
>                   I might be able to verify whether it's PQ14970 from
> that.
> Thanks, Bob La Brie ADSM Development
>
>
>
>
>
>
> ADSM-L AT VM.MARIST DOT EDU on 04/22/98 06:48:00 AM
> Please respond to ADSM-L AT VM.MARIST DOT EDU
> To: ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject: Hung Server
>
>
> ADSMer's,
>
>         Let's get the technical info out of the way:
>
> Server: OS/390 V3 R1
> Clients: NT 4.0, Novell 3.x, 4.x, V3 R1
>
>         I need some help with a problem we had last night.  I saw a
> post
> similar to my problem, and was wondering what the outcome was.  Last
> night when the backups starting running, the clients established
> sessions with the server.  It appeared that even though the sessions
> were established, no tapes were being written to.  As more and more
> schedules kicked off, more sessions started until we hit our
> Maxsessions
> threshold.  We tried to cancel the sessions, but that did not work.
> We
> had to bring the ADSM server down and back up, and bounce all the
> Services and Schedulers.  The backups ran fine after that.  We did not
> see any error messages at all???  Any help would be much appreciated.
>
> Thanks in advance,
> Rick Smith
> Maritz, Inc.
> Storage & Security Administration
> smithrr AT maritz DOT com
> (314) 827-1584
>
>
>
>
<Prev in Thread] Current Thread [Next in Thread>