An update for those watching this thread...

Michel discovered that the time setting of his server
and his client were an hour off, and so he wasn't looking
in the correct portion of the TSM Server activity log to find
the messages.  Once he looked in the TSM Server log
more closely, he found that TDP for Exchange was
logging the failure messages correctly.

Thanks,

Del

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

"It's a beautiful day.  Don't let it get away."  -- Bono




                    Michel Engels
                    <Michel.Engels@DE       To:     ADSM-L AT VM.MARIST DOT EDU
                    VOTEAM.BE>              cc:
                    Sent by: "ADSM:         Subject:     TDP Exchange gives out 
of storage
                    Dist Stor
                    Manager"
                    <[email protected]
                    .EDU>


                    05/09/2001 07:17
                    AM
                    Please respond to
                    "ADSM: Dist Stor
                    Manager"





I am testing the TDP for Exchange in an environment. Everything works fine.
We
can do full, incr backups. We do save the backups directly to a VTS atached
to
the Mainframe. Now the number of scratch tape defined for the storagepool
has
reached the maximum. I can add some tapes but my problem is the message
that the
server is out of storage (ANS1329S) is only trapped on the client and not
on the
server. The batch can give an %errorlevel% = 306 and the excdsm.log does
show
the message but the actlog does not show the problem.

Is there any possibility to send this message to the server? Do I have to
install some mail uitility on the client to be able to inform the people
concerned about the fact that the backup in not complete?


TSM Client 3.7.2 on WinNT
TDP for Exchange V1.1.1.0
TSM Server V3.7.1 on OS390

M Engels