Zoltan,

My server is Windows, but had the exact problem - clients failing with
ANS1316E when the server recovery log is obviously not full, and the server
doesn't go down (which it would if truly out of log space).

Look at IC63373.

Local fix (which is to reset a DB2 variable) seems to have solved it, we've
gone 5 days now without the failure (longest so far, she said with fingers
still crossed...)  If you issue the DB2 GET DB  CFG as shown in the APAR, it
will at least display the variable and you can see if the problem applies.

W

On Tue, Oct 27, 2009 at 9:27 AM, Zoltan Forray/AC/VCU <zforray AT vcu DOT 
edu>wrote:

> Another failure with my V6.1.0.2 server.
>
> This morning the ONLY user (a total of 3-active nodes) of my V6.1.2.0
> server reported his backups failing with his dsmerror.log showing:
> 10/26/2009 23:21:15 ANS1316E The server does not have enough recovery log
> space to continue the current operation
> The activelogsize is set to 60000 and I run 3-FULL DB backups daily
> (followed by BACKUP VOLHIST).  This mornings check shows the log at under
> 200MB used (a full DB backup had already run at 22:00:00).
> How big do I need to make this?  Should I max it out at 128G?
> What are your experiences/settings for activelogsize, for folks running a
> V6 server in production?
>