Thank for reply Del ,
I checked Tivoli knowledge base and I find following for TDP for SQL


APAR= IC31171  SER=                            IN INCORROUT
PROBLEM IN TSM API THAT CAN CAUSE TDP FOR SQL TO FAIL BACKUP
W/ ERROR ACO0302E A FAILURE OCCURED ON STRIPE NUMBER (0),RC=418

Status: CLOSED                              Closed: 08/07/01

Apar Information:

RCOMP= 5698TSMCL    TIVOLI STR MGR  RREL= R42W
FCOMP= 5698TSMCL    TIVOLI STR MGR  PFREL= F999  TREL= T
SRLS:      NONE

Return Codes:

Applicable Component Level/SU:
R42W PSY         UP
R42E PSY         UP
R42N PSY         UP

Error Description:
Backups with TDP for SQL are failing on some database with
the following errors:
ACO0302E A failure occured on stripe number (0), rc = 418
 ANS0322E (RC39)   no text available for this return code.
.
RC=39 means DSM_RS_ABORT_SYNTAX_ERROR.

.
Trace shows:
 dsmapi.cpp(2050):Exit DDsmApi::ddsmEndTxn(), rc = 2302
 backupdb.cpp(5142):DSMENDTXN() failed, rc = 2302,
                    endTxnReason = 39
 backupdb.cpp(5157):Calling AGTDSMRCMSG( 39 )
 ...
 backupdb.cpp(5174):DSMENDTXN() failed, (rc or endTxnReason)=39
     msg = ANS0322E (RC39)   no text available for this return
     code.
 backupdb.cpp(5211):Meta data or rename processing failed
     on stripe number 3m_ConsumerErrorMsgP: ANS0322E (RC39) no
     text available for this return code. metaDataBackupRc : 418
.
The activity log will show:
 ANR9999D smnode.c(9619): Both merge(1) and forceMerge(1) are
 not allowed
 ANE4993E (Session: 1866, Node: NodeName)  TDP MSSQLV2 NT
  ACO3002 TDP for Microsoft SQL Server: full backup of
  database <DB_NAME> from server MTG21004 failed, rc = 418

.
This problem occured on TSM Client/API level 4.1.2.14, TSM
Server is 4.1.4.0, and TDP for SQL 2.2.
.

Local Fix:
None


Problem Summary:
****************************************************************
*USERS AFFECTED:TSM API client                                 *
****************************************************************
*PROBLEM DESCRIPTION:                                          *
* PROBLEM IN TSM API THAT CAN CAUSE TDP FOR SQL TO FAIL BACKUP *
* W/ ERROR ACO0302E A FAILURE OCCURED ON STRIPE NUMBER (0)     *
* RC=418                                                       *
****************************************************************
*RECOMENDATION:                                                *

****************************************************************

Temporary Fix:
The customers which use TSM client V4.1 can download Windows
fixtest 4.1.3.11 for this problem.

Comments:
MODULES/MACROS:   EXE      DSMAPI
                  EXE      DSMC

Problem Conclusion:
The problem has occured because some reserved fields of
BackrenameEnhanced verb have not been set to 0s before
the verb building and contained garbage. The fix was made to set
all reserved fields with 0s.

Do you think that TDP for Exchange can be affected by this error ?
Can I replace API for TDP ?

Regards
           Petr



----- Puvodnm zprava -----
Od: "Del Hoobler" <[EMAIL PROTECTED]>
Komu: <[EMAIL PROTECTED]>
Odeslano: 24. zarm 2001 16:52
Predmet: Re: MS Exchange backup problem


> > I just ended new installation of TSM server 4.2 on OS/390 with Exchange
> > clients
> > with TDP for Exchange version 2.2 - from time to time full backup ends
> > with error ( from TSM server log ) ANE4993E and ACN3502 with rc=418
> > ( TSM B/A client 4.2.0 ) on NT4 and Win2000 . No additional messages in
> > TSM server log.
>
> Petr,
>
> You will need to look at the machine running
> TDP for Exchange... and examine the tdpexc.log file
> and the dsierror.log file to find out why
> TDP for Exchange thought there was a problem.
> RC=418 is a generic "TSM API error".
> The dsierror.log file might provide some information.
>
> Thanks,
>
> Del
>
> ----------------------------------------------------
>
> Del Hoobler
> IBM Corporation
> [EMAIL PROTECTED]
>
> "It's a beautiful day.  Don't let it get away."  -- Bono

Reply via email to