When you encounter that error, check your password files in /etc/adsm.
The password file will be named the same as your SERVERNAME for the stanza
in DSM.SYS which your UBD backups use. If the password file is missing,
then you need to figure out how it is getting deleted. If the date has
changed, then you need to see what may be causing it to change.
Didn't really tell you why it is happening, but maybe that will help in
determing that.
James Thompson
>From: Ross Davies <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: DSMAPIPW for UDB backups on Solaris 2.6
>Date: Thu, 15 Mar 2001 15:15:46 +1100
>
>We are using TSM to back up our DB2 UDB databases on Solaris 2.6 clients.
>On the TSM server I have set the password expiry for all of the Solaris
>nodes to 9999.
>However after a varying number of days the DB2 backups start failing with
>137 api return codes
>which are fixed by running the dsmapipw password setting job. We ran this
>job when
>the nodes were first backed up but every so often we have to run it again.
>In the manuals it states
>that the dsmapipw password setting job only ever needs to be run once. Why
>do we have
>to continually run this job? I have passwordaccess generate.
>
>Thanks
>Ross Davies
>Tuning & Storage Admin
>Centrelink
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
