The delay should have just been a block and not an abort.

The "data transger interrupted" supposedly means there was an error or
abort while trying to write to the storage media.

I'd look in the operating system error logs, and for more context in the
actlog.


On 06.03.09 at 09:28 andyc AT ANDYC.CARENET DOT ORG wrote:

Date: Thu, 9 Mar 2006 09:28:52 -0600
From: Andrew Carlson <andyc AT ANDYC.CARENET DOT ORG>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: ANR2997W Causing Transaction Failure

Has anyone ever seen ANR2997W cause a transacton failure?  Here is a
snippet of my log:

03/08/06   14:39:10      ANR2997W The server log is 80 percent full. The
server
                        will delay transactions by 3 milliseconds.
(SESSION:
                        152212, PROCESS: 1586)
03/08/06   14:39:10      ANR0524W Transaction failed for session 143862
for node
                        UPBCCLND02 (DB2/6000) -  data transfer
interrupted.
                        (SESSION: 143862)
03/08/06   14:39:10      ANR0514I Session 143862 closed volume 110721.
(SESSION:
                        143862)


This session is a very long running session and is probably the one that
had the log pinned.  I am running TSM 5.3.2.3 on AIX 5.2.5.  y recovery
log is 12,284MB.  Thanks for any information.