Dianne,
        I've seen the same thing happen on a couple of occasions.  Sometimes,
like you've seen, the only thing running at the time was a hung ADSM
session with a Netware client - on one or two other occasions, there
wasn't anything else running.  I haven't had time to pursue with IBM
support yet .

Tim Pittson
tpittson AT himail.hcc DOT com

>----------
>From:  Dianne Sharp[SMTP:DSHARP AT CLEAR.CO DOT NZ]
>Sent:  Thursday, May 08, 1997 9:40 PM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       ADSM Recovery Log filling up
>
>We're running ADSM Server V1 for MVS.
>
>Last night, our ADSM Recovery Log filled up, causing several backups to
>be missed.
>When I did a Q SESS command, there was only one active session showing
>for a Netware client which had been in a Wait state for over 12 hours.
>Investigating the logs on that client, I figured out that a session
>started at 18:30.  Then at 19:39 there was a TCP/IP connection failure.
>A retry occured and another session was established at 19:59 and the
>backup completed OK.  However, the first session was never stopped.
>
>I cancelled the "hung" session and the recovery log was still over 96%
>full, so I ended up restarting the ADSM Server and the recovery log
>utilisation went down to under 1%.
>
>My theory is that the "hung" session somehow caused the recovery log to
>fill.  Has anyone else experienced the same problem?  If so, what's the
>solution?
>
>Dianne Sharp
>Operations Analyst
>ISS CUSTOMER SUPPORT
>Ext 4208
>