Invalid password only when in stream commands with DSMADMC

[DavidDiepUSC]

Hi Everyone,

First off, here is my system:

RHEL 6.4
zSeries Mainframe
TSM server is 7.1.3
TSM client is 6.4

I tried searching and could not find any hits for this particular problem. Maybe someone has had this issue in the past...

When I log in direct after invoking dsmadmc, I log in without issues:

# dsmadmc
IBM Tivoli Storage Manager
Command Line Administrative Interface - Version 6, Release 4, Level 0.0
(c) Copyright by IBM Corporation and other(s) 1990, 2012. All Rights Reserved.

Enter your user id: david.diep

Enter your password:
Session established with server TSM04: Linux/s390x
Server Version 7, Release 1, Level 3.0
Server date/time: 11/07/2018 13:20:54 Last access: 11/07/2018 13:16:37


tsm: TSM04>quit


However, when I try this, I fail with an invalid password:

# dsmadmc -id=david.diep -password=******** query node
IBM Tivoli Storage Manager
Command Line Administrative Interface - Version 6, Release 4, Level 0.0
(c) Copyright by IBM Corporation and other(s) 1990, 2012. All Rights Reserved.

ANS1051I Invalid password
ANS8023E Unable to establish session with server.

ANS8002I Highest return code was 137.

What do you guys think? What am I doing wrong?

Thanks,

David

 

[LED888]

Syntax wise, it is correct.
The only thing I can think of is a possible typo with the password.
Are we using the dsmadmc in the server directory or the TSM B/A Client directory?
If we are using the dsmadmc in the server directory, try the one in the TSM B/A Client directory.
That is if we also install the dsmadmc via the TSM B/A Client.
When we install the TSM B/A Client, the dsmadmc is not installed by default.

If we are using the dsmadmc in the TSM B/A Client directory, try one on that is in the server directory.
The dsmadmc is installed in two locations in the server directory, may need to do a find of where they are located.

There is a known issue with the dsmadmc but not regarding with the password.
The issue was address at 7.1.1.0, and we are above that.

Server APARs fixed in the IBM Spectrum Protect Version 7.1 fix pack levels

On the system that is hosting a TSM B/A Client, if the dsmadmc is installed, attempt to log into the server and see if the issue follows.

If the results are still the same.
May need to open a call with IBM Support, to check it out.

Good Luck,
Sias

 

[DavidDiepUSC]

Hi Sias,

I'm sure its the same password... its only a matter of passing it instream or by prompt from dsmadmc. I'll try installing a newer client and see if that resolves the issue.

Thanks,

David

 

[DavidDiepUSC]

Hi, I upgraded the client but the problem persists.



[@TSM04 linux390]# dsmadmc
IBM Tivoli Storage Manager
Command Line Administrative Interface - Version 7, Release 1, Level 3.0
(c) Copyright by IBM Corporation and other(s) 1990, 2015. All Rights Reserved.

Enter your user id: david.diep

Enter your password:

Session established with server TSM04: Linux/s390x
Server Version 7, Release 1, Level 3.0
Server date/time: 11/08/2018 13:39:20 Last access: 11/08/2018 12:49:37


tsm: TSM04>quit

ANS8002I Highest return code was 0.

[@TSM04 linux390]# dsmadmc -id=david.diep -password=p@$$word q node
IBM Tivoli Storage Manager
Command Line Administrative Interface - Version 7, Release 1, Level 3.0
(c) Copyright by IBM Corporation and other(s) 1990, 2015. All Rights Reserved.

ANS1051I Invalid password
ANS8023E Unable to establish session with server.

ANS8002I Highest return code was 137.

[root@TSM04 linux390]#


Sure enough, the active log shows that the password was incorrect:

11/08/2018 13:39:44 ANR0407I Session 3740 started for administrator
DAVID.DIEP (LinuxZ64) (Tcp/Ip
hs-tsm04.in.dc.gov(46395)). (SESSION: 3740)
11/08/2018 13:39:44 ANR0418W Session 3740 for administrator DAVID.DIEP
(LinuxZ64) is refused because an incorrect password was
submitted. (SESSION: 3740)
11/08/2018 13:39:44 ANR0405I Session 3740 ended for administrator DAVID.DIEP
(LinuxZ64). (SESSION: 3740)

 

[Trident]

Any funny characters in your password? Try setting one with only numbers and letters

 

[DavidDiepUSC]

Hi Trident... yep, I had funky characters. I changed it to lowercase alphanumerics and that did the trick!

Thanks for all your responses.

 

[marclant]

Hi Trident... yep, I had funky characters. I changed it to lowercase alphanumerics and that did the trick!

Thanks for all your responses.

I bet that`s the OS interpreting that special character as a wildcard in the command.