TSM Admin CLI "points" to wrong TSM server

GrumpyBob

ADSM.ORG Member
Joined
Jun 24, 2008
Messages
21
Reaction score
0
Points
0
PREDATAR Control23

Hi All

This is, I suspect a very basic question so apologies, in advance, for that.

We have 2 TSM servers named TSM1 and TSM2. It used to be the case that when I launched the TSM Admin CLI (C:\Program Files\Tivoli\TSM\baclient\dsmadmc.exe) on TSM2, it would be “for” TSM2 (i.e. the prompt would read tsm: TSM2>) but, recently, it has started to always connect to TSM1.

I realise I can get around this by always prefixing commands with TSM2: but this is a bit of a pain and I’d like to resolve it properly and understand how this happened.

As I say, I suspect the answer I embarrassingly simple but I haven’t had any success from Googling around the subject.
 
PREDATAR Control23

If it switched, somebody edited dsm.opt.


- make a copy of dsm.opt, name it dsm2.opt, edit the option file to point to TSM2. When you want to point to TSM2, use: dsmadmc -optfile=dsm2.opt You can do the same for the client: dsmc -optfile=dsm2.opt

- or you can specify the tcps and tcpp in the command:
dsmadmc -tcpserveraddress=x.x.x.x tcpport=xxxx
 
Top