Hello Robert !
Thanks for the answer - but I solved the problem last thursday.
I think information in README for V.1.1.1.1 are misleading
the part : additional notes should be removed/replaced
in this part is a statement like ..... note that the
.../ibmpow/latest was removed.
that is nor correct.
after some frustrating days I got this infomations from IBM Mainz ADSM/TSM
Support
We have found several other pmrs reporting the same problem. The
resolution was the following.
1. Copy the DSM.SYS and DSM.OPT to another directory like /home
Any INCLUDE/EXCLUDE list you may have for the Backup Archive
Client and API.
2. Uninstall ADSM client , API and TDP for Domino
3. Install ADSM Client including TDP and the API which came with
TDP.
4.Then verified connection to ADSM Server
5. Run Domsetup
6. Then make sure paths are correct. < /opt/lotus/notes/latest/ibmpow
> should be set before < /usr/lotus/bin>
Then do $domdsmc que adsm
$domdsmc que dom
.
The only think to correct the problem was indead Nr. 6
Mit freundlichen Gruessen - Yours sincerely
Manfred Eber
GE CompuNet Ludwigshafen
System Engineering
Germany
E-Mail : manfred.eber @ gecits-eu.com
http://www.gecits-eu.com
This email is confidential. If you are not the intended recipient,
you must not disclose or use the information contained in it.
If you have received this mail in error, please tell us
immediately by return email and delete the document.
Robert Delaney <[EMAIL PROTECTED]> on 27.11.2000 15:56:09
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: Manfred Eber/Ludwigshafen/GECITS-EU)
Subject: Re: TDP for Domino V.1.1.1.1 problems
------------------------------------------------------------------------------
Hi Manfred,
Domino is picky about what is and what isn't in the PATH. My guess is
that's the problem.
I don't see the actual error in any of your attachments. Are you seeing a
4103 error code?
Try taking out the "/opt/lotus/bin" and the "opt/lotus/bin/tools"
directories. Also, the symbolic link to domdsmc MUST be from the
/opt/lotus/notes/latest/ibmpow directory, not from the /opt/lotus/bin. The
"domsetup" script puts that link there. /opt/lotus/notes/latest/ibmpow
should be first in your PATH.
If this doesn't help, set up to run with the lotus "wrapper script" (5
steps) as described in the latest README for TDP for Domino.
If that still doesn't do it, you should contact service to get the proper
traces and environment doc.
Bob Delaney
TDP Client Development
Manfred Eber <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 11/22/2000
07:31:55 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: TDP for Domino V.1.1.1.1 problems
Hello !
I�ve to deal with the implementation of TDP for Domino
AIX 4.3.3 , TSM 3.7.3.8 , TDP V.1.1.1.1 , Domino 5.0.4
TDP doesn�work properly in the test environment in my home office.
I�ve read the manuals , redbooks ( newest redbook ), README�s , newest
README�s.
Checked the environment lot�s of times. -> domsetup ...
I can only get in contact with TDP trough TSM API to TSM Server.
But I can�t connect properly to Domino with commands like
domdsmc query domino
I cannot contact the Domino server - done the things like written in the
last
Fix README in additional information.
the Domino Setup was ok - Admin Client is working
I�ve tried all the hints - doesn't work.
in the last README ( V.1.1.1.01 )
what�s about the Lotus Domino executables.
in the last fix README is written to have a to path /opt/lotus/bin
and
the directory where the notes.ini is stored.
here are some config�s
one of the them : domout is a AIX watch output.
( i added my domino user dom2 to the group audit , so I can do this )
$ watch -o domout domdsmc query domino from domino data directory.
(See attached file: domout_dom2)
you can see , the fail is that <server> couldn�t be loaded/contacted
in any path ( in the the path is too /opt/lotus/bin ) , lool in
.profile.
where some hints from the last redbook are commented out.
some other infos
(See attached file: .profile)(See attached file: domdsm.log)
what can be done ?
first I can configure TDP for one Server to check it out.
then I have to configure TDP for Domino for 3 partioned Servers.
Any suggestion are welcome.
Best would be a really running example config
thanks
Mit freundlichen Gruessen - Yours sincerely
Manfred Eber
GE CompuNet Ludwigshafen
System Engineering
Germany
