Hi

Have the same problem here, but on a Solaris client. TSM support haven't
helped us, but I noticed when we changed the nodename to something shorter
it worked...
A workaroud is to have password xxxx in dsm.sys

If you find a solution please let me know

Regards
Niklas

-----Original Message-----
From: Eric Winters [mailto:ewinters AT AU1.IBM DOT COM]
Sent: den 25 september 2002 09:58
To: ADSM-L AT VM.MARIST DOT EDU
Subject: sessOpen: Error 137 from signon authentication


Dear All,

I have an AIX node with TSM Backup client at 4.2.1.0 and a TSM server on AIX
at 4.2.1.10

I have PASSWORDACCESS GENERATE set in the dsm.sys, and I've set a
PASSWORDDIR. The first time I attempt to run a dsmc command as root, I'm
naturally asked to provide password details. This works fine and my command
runs successfully. A TSM.PWD file is created as expected. But when I run my
next dsmc command I have to provide the password all over again. And the
dsmerror.log shows the following message....
 sessOpen: Error 137 from signon authentication

The baffling thing is that I have this working just fine on another node at
the same level of client s/w talking to the same server.

Any ideas?
Thanks people,


Regards,

Eric Winters
Sydney Australia