Hi,

 I've got an issue with a DB2 database running backup towards a TSM
server... for some wierd reason, it keeps dropping/re-establishing the
connection towards the server...
The activity log on the server says:

01/24/06 12:57:21     ANR0406I Session 196229 started for node NODENAME
                        (DB2) (Tcp/Ip ww.xx.yy.zz(19643)).
                       (SESSION: 196229)
01/24/06 12:57:21     ANR0480W Session 196229 for node NODENAME_FRISKDB
                       2_DB2 (DB2) terminated - connection with client
severed.
                       (SESSION: 196229)
01/24/06 12:57:34     ANR0406I Session 196234 started for node NODENAME
                        (DB2) (Tcp/Ip ww.xx.yy.zz(19645)).
                       (SESSION: 196234)
01/24/06 12:57:34     ANR0480W Session 196234 for node NODENAME_FRISKDB
                       2_DB2 (DB2) terminated - connection with client
severed.
                       (SESSION: 196234)
01/24/06 12:57:46     ANR0406I Session 196236 started for node NODENAME
                        (DB2) (Tcp/Ip ww.xx.yy.zz(19646)).
                       (SESSION: 196236)
01/24/06 12:57:47     ANR0480W Session 196236 for node NODENAME_FRISKDB
                       2_DB2 (DB2) terminated - connection with client
severed.
                       (SESSION: 196236)
01/24/06 12:57:59     ANR0406I Session 196238 started for node NODENAME
                        (DB2) (Tcp/Ip ww.xx.yy.zz(19649)).
                       (SESSION: 196238)
01/24/06 12:58:00     ANR0480W Session 196238 for node NODENAME_FRISKDB
                       2_DB2 (DB2) terminated - connection with client
severed.
                       (SESSION: 196238)
01/24/06 12:58:12     ANR0406I Session 196240 started for node NODENAME
                        (DB2) (Tcp/Ip ww.xx.yy.zz(19653)).
                       (SESSION: 196240)
01/24/06 12:58:12     ANR0480W Session 196240 for node NODENAME_FRISKDB
                       2_DB2 (DB2) terminated - connection with client
severed.
                       (SESSION: 196240)

What could be the cause of this ?? The DB2 is the only node having this
problem - all other nodes runs without problems...

Regards,
/Brian