Funny behaviour of DB2-userexit db2uext2

Hi TSM'ers
Env:
TSM-Server: AIX 5.3 ML 4, 64 bit
TSM-Client: AIX 5.3 ML 4, TSM 5.3.4.0, API at the same level, 32 bit
ICM       : 8.3.0 IBM Content Manager
DB2       : 8.1.1.104

Desc:
1. recently installed IBM's Content Manager using DB2 and TSM via the
   "db2uext2".
2. Setting the "LOGRETAIN ON" and "USEREXIT ON" in the DB2-config
3. Running successfully  incremental and full backup's
   (checked via LIST HISTORY and via db2adutl )
4. Accordingly to IBM'S RedBook
        Backing Up DB2 Using Tivoli Storage Manager, June 2001
        Chapter 10, pp 208-210
   we ran
        db2 restore database icm22 use tsm taken at 20060629142959
   from a FULL ONLINE backup working as expected and leaving the DB in
        "Rollforward pending    DATABASE"
5. Trying to run the
        db2 rollforward database icm22 to end of logs and stop
   ended:
SQL1268N  Roll-forward recovery stopped due to error "21" while retrieving
logfile "S0000306.LOG" for database "ICM22" on node "0".

6. Diving into
        /icmdb/db2inst1/sqllib/db2dump/db2diag.log
we found the first occurence of "rc = 21":

---->>>>>>>>>>>>
2006-03-01-17.30.05.597600+060 I33398913C395      LEVEL: Error
PID     : 643126               TID  : 1           PROC : db2logmgr (ICM22)
0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0000000.LOG to USEREXIT from
          /icmdb/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/ with rc =
21.

2006-03-01-17.30.05.597827+060 I33399309C370      LEVEL: Warning
PID     : 643126               TID  : 1           PROC : db2logmgr (ICM22)
0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgRetryFailedArchive, probe:4780
MESSAGE : Still unable to archive log file 0 due to rc 21 for LOGARCHMETH1
          using method 4 and target .
----------->>>>>>>>>>>>>>

and repeating this message up today, i.e.

2006-06-30-16.32.19.648066+120 I736430021C394     LEVEL: Error
PID     : 327834               TID  : 1           PROC : db2logmgr (RM22)
0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0000000.LOG to USEREXIT from
          /icmdb/db2inst1/db2inst1/NODE0000/SQL00002/SQLOGDIR/ with rc =
21.

2006-06-30-16.32.19.648292+120 I736430416C369     LEVEL: Warning
PID     : 327834               TID  : 1           PROC : db2logmgr (RM22)
0
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgRetryFailedArchive, probe:4780
MESSAGE : Still unable to archive log file 0 due to rc 21 for LOGARCHMETH1
          using method 4 and target .

BUT, NO reference to
        S0000306.LOG


7. I checked "db2uext2.c" again and found only ONE change in the
        #define AUDIT_ERROR_PATH "/icmdb/db2inst1/tsm/"
   which suits our installation paths

8. If I look for the "rc = 21" via
        grep 21 /usr/tivoli/tsm/client/api/bin/sample/dsmrc.h|head -1
   I get:
        #define DSM_RS_ABORT_NODE_ALREADY_DEFED      21
   Google'ing for  "DSM_RS_ABORT_NODE_ALREADY_DEFED"
   which tells me that db2ext2 is trying to open a new node via "open
   registration"

Questions:
1. Is my conclusion with "open registration" in 8. OK or is it just a
   misinterpretation ?
2. Has anybody out there had this problem ?

With some hope for a good idea,
Peter
-- 
MfG / Ciao         - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Peter Dümpert                                   Email: p.duempert AT tu-bs DOT 
de
Rechenzentrum der Technischen Universität       Fax  : ++49/531/391-5549
D 38092 Braunschweig                            Tel  : ++49/531/391-5535