Joel,

309 means the ADSM API operation was cancelled for some reason.
310 means some type of Exchange error was encountered.

As you stated, looking at the excdsm.log is really the
best way to find out for sure what caused the specific return code.
That should be your procedure when things go wrong.

Detailed logging is maintained on the machine running
the Exchange Application Client program.

The TSM Server log that you quoted records main events that
occurred during the backup or restore but is not meant
to repeat all of the detailed information/logging data that is
contained in the Exchange Application Client log.

That is how it works today.

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com


"Cooper, Joel (US - Hermitage)" <jocooper AT DTTUS DOT COM>@VM.MARIST.EDU> on
03/24/2000 08:10:19 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: TDP for Exchange return codes



Del,
Thanks for the reply.
I was trying to establish if there was a correlation to the #s.
For instance, I got this 2x yesterday:

03/23/2000 21:43:55  ANE4991I (Session: 6433, Node: USCNTNT404A_EXCH)  TDP
                      MSExchg NT ACN3521 Exchange Application Client: FULL
                      backup of IS from server USCNTNT404 failed, rc = 309.

I think in both cases the operation was cancelled by the user. Both had
"309".
I also am getting occasional 310s, etc.

But there is no way to use the error code to shed light on the failure?
It is the excdsm.log that documents a cancellation.
Joel