Really harsh...
However, the problem doesn't necessarily lie w/in the product, but the lack of
documentation. I went thru this heartache myself. Once you figure it out,
everything does work relatively smoothly.
But the "getting there" for the first time is no picnic.
Regards, Joe
-----Original Message-----
From: Steve Harris [mailto:Steve_Harris AT HEALTH.QLD.GOV DOT AU]
Sent: Tuesday, April 29, 2003 8:00 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: ANS1217E message from TDPO
Harsh words Tom.
The basic problem is that any product that uses the API must use PASSWORDACCESS
PROMPT and come up with some method to encrypt the password locally so this it
can be supplied this when asked by the
api.
BA client, however can use PASSWORDACCESS GENERATE and most users do.
So, the workaround for sharing the same node name between BA and API is to
specify PASSWORDACCESS PROMPT on the BA client, and embed the password in the
BA Client dsm.opt file.
Regards
Steve Harris
AIX and TSM Admin,
Queensland Health, Brisbane Australia
>>> Thomas.Denier AT MAIL.TJU DOT EDU 30/04/2003 0:50:57 >>>
I have resolved the problems described in my previous posting, and in
the process discovered another problem. API clients use a dsm.sys file
in a different directory from the dsm.sys used by the backup/archive
client. Once I figured this out, I was able to change the 'passwordaccess'
line in the API dsm.sys. I also added a 'nodename' line. Tivoli recommends
using a separate node name for TDP for Oracle. I tried arranging for
this using the TDPO_NODE option in tdpo.opt, but this option never had
any effect on the output from "tdpoconf showenv". Once I got the desired
output from that command, I set about running "tdpoconf password". I was
consistently getting authentication failures. Checking the TSM server
logs revealed that TDP was trying to connect using the node name originally
set up for the backup/archive client. Inserting the TDPO_NODE option again
fixed this. In short "tdpoconf showenv" and "tdpoconf password" use
different algorithms for determining the node name to be used. That
strikes me as conclusive grounds for installing SQL/BackTrack and telling
Tivoli that we will reevaluate TDP for Oracle when and if they get some
grown-ups involved in developing it.
**********************************************************************
This e-mail, including any attachments sent with it, is confidential
and for the sole use of the intended recipient(s). This confidentiality
is not waived or lost if you receive it and you are not the intended
recipient(s), or if it is transmitted/ received in error.
Any unauthorised use, alteration, disclosure, distribution or review
of this e-mail is prohibited. It may be subject to a statutory duty of
confidentiality if it relates to health service matters.
If you are not the intended recipient(s), or if you have received this
e-mail in error, you are asked to immediately notify the sender by
telephone or by return e-mail. You should also delete this e-mail
message and destroy any hard copies produced.
**********************************************************************
|
