> "DS" == Dianne Sharp <DSHARP AT CLEAR.CO DOT NZ> writes:

DS> We're running ADSM Server V1 for MVS.  Last night, our ADSM
DS> Recovery Log filled up, causing several backups to be missed.
....
DS> I cancelled the "hung" session and the recovery log was still over
DS> 96% full, so I ended up restarting the ADSM Server and the
DS> recovery log utilisation went down to under 1%.

DS> My theory is that the "hung" session somehow caused the recovery
DS> log to fill.  Has anyone else experienced the same problem?  If
DS> so, what's the solution?


I experienced similar problems this week, but I thought that the
recovery log hanging full was related to some TEMP disk errors I was
getting on one of the database mirrors.  I ran some diagnostics on the
drive and decided to replace it, but the ADSM database seems to be
fine.

As Dianne found, the recovery log cleared itself when dsmserv was
restarted.

A day later, I found a hung dsmc on an AIX workstation, so perhaps the
recovery log problem was indeed related to the hung dsmc.