Try finding your password file, I think it's /etc/security/adsm by default, but you might double check that. Try deleting it, then try passwordaccess generate again. Also, is your nodename, hostname, and password different? If not, I vaguely recall something about the encryption processes failing sometimes if those are the same.
Once you've got those addressed, you should just be able to set passwordaccess generate, do a dsmc, do some command that accesses the server, it'll ask for nodename and password. Enter them, then quit. That's all it should take to store the new encrypted password. You should then be able to do a dsmc sched and it should start right up. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -----Original Message----- From: Luscombe John (HS) [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 27, 2002 8:00 AM To: [EMAIL PROTECTED] Subject: Passwordaccess generate failing Hi listers, You'll have to forgive me, I'm a bit of a TSM novice. We have TSM 4.2.something running under AIX. Our DB2 guy had a problem moving a table from one client node to another. He did some reading that suggested changing the password at the server to a known value, and switching off passwordaccess generate at the client. I did this, no problems, he was able to restore his tables. The problem now is, how do I get it back to the way it was before? I've done some reading through archives, but must be missing something. When I have passwordaccess prompt, I can do a dsmc sched, and enter the userid and password as set on the server, no problems. But as soon as I switch on access generate and do a dsmc sched and enter the userid, then it bombs immediately. I'm guessing what's happening is that the client is sending the encrypted password back to the server which of course doesn't match. But how do I get them back in sync. Thanks for your help Frustrated beginner.
