If I do remember well you have to delete the file named SERVERNAME in the
/etc/security/adsm directory.
When the option is set to PASSWORDACCESS GENERATE you have to execute a dsmc q
ses and enter the password for that node.
The next step is to set the password in the initSID.bki file with the backint -p
/oracle/SID/dbs/initSID.utl -f password command which has to be executed as
orasid user. This will store the new password.
Hope this helps,
Michel Engels
TSM Consultant
Devoteam Belgium
Wolfgang Herkenrath <[EMAIL PROTECTED]> on 04/23/2001 02:54:12 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: Michel Engels/BE/Devoteam)
Subject: TDP 3.1 and PASSWORDACCESS GENERATE
Hi *'SM'ers,
I installed TDP 3.1.0.5 on a TSM-Client 3.7.20 (AIX 4.3.3).
After some starting problems the client is now able to backup.
But now I've got the following problem:
At my dsm.sys file in /usr/tivoli/tsm/client/api/bin I set the passwordaccess to
prompt. All works fine.
But when I change the passowordaccess to generate the passwordverification
fails. The passwordrequired parameter at the util-file is set to no (like it is
discribed at the documentation).
So, I changed the password for the client at the server. I start dsmc with
root-user and tipe the new password. So far so good.
Now I run the command 'backint -p initSYS.utl -f password' to set the password
for TDP. But it failes.
Are there any ideas why my normal dsmc session works and the backint call
failed?
TIA
Wolfgang
