1) Updated the password definition on the new server 2) Make sure your existing client is actually pointing to the new TSM server (dsm.sys)
3) If the passwords are different on each TSM server then the TSM client scheduler will have to be updated on the client. You can use the wizard or the dsmcutil cmd to update the password on the client. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant -ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED] -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Hunley, Ike Sent: Tuesday, January 07, 2003 11:29 AM To: [EMAIL PROTECTED] Subject: Client password problem I moved server backups to a different MVS TSM. Now each time the server attempts to access TSM I get the dreaded 137 authentication failure. I've added password access generate to DSM.SYS and recycled the TSM scheduler several times. What else can I do to correct this? Blue Cross Blue Shield of Florida, Inc., and its subsidiary and affiliate companies are not responsible for errors or omissions in this e-mail message. Any personal comments made in this e-mail do not reflect the views of Blue Cross Blue Shield of Florida, Inc.
