Hi Efim,

You can just connect to a replica server (dsmc), without any warning. I don't 
know at which point this ANS2112I is thrown.
Thanks for your help!

Kind regards,
Eric van Loon
Air France/KLM Storage & Backup

-----Original Message-----
From: ADSM: Dist Stor Manager <ADSM-L@VM.MARIST.EDU> On Behalf Of Efim
Sent: vrijdag 22 januari 2021 18:00
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Client configuration scripts

HI,
Maybe you should try checking the client message when connecting, for example 
ANS2112I?
Efim

> On 22 Jan 2021, at 19:31, Loon, Eric van (ITOP NS) - KLM 
> <eric-van.l...@klm.com> wrote:
> 
> Hi everybody,
> 
> We are running multiple servers. Both our Windows and Linux departments use 
> their own scripts to configure new (or reinstalled) clients. The script tries 
> to connect to each TSM/SP server sequentially and if a connection is 
> successful, the client is configured for that specific server. This has 
> always been working fine, until we added two servers with client replication. 
> In this case, a client node exists on two servers, but only one of them is 
> valid: the one with the node in replmode=send. Technically a client can 
> connect to both the primary server and the replica server, so the first one 
> in line is used by the script, which might be the wrong one (replica).
> Has anybody found a solutions to overcome something like this? I thought of 
> using a SQL query through the admin client, but that means that the admin 
> client has to be installed on all clients and an admin userid/password has to 
> be included in the scripts. Not the safest solution, I think.
> Thanks for any reply in advance!
> 
> Kind regards,
> Eric van Loon
> Air France/KLM Storage & Backup
> ********************************************************
> For information, services and offers, please visit our web site: 
> http://www.klm.com. This e-mail and any attachment may contain confidential 
> and privileged material intended for the addressee only. If you are not the 
> addressee, you are notified that no part of the e-mail or any attachment may 
> be disclosed, copied or distributed, and that any other action related to 
> this e-mail or attachment is strictly prohibited, and may be unlawful. If you 
> have received this e-mail by error, please notify the sender immediately by 
> return e-mail, and delete this message.
> 
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
> employees shall not be liable for the incorrect or incomplete transmission of 
> this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
> Airlines) is registered in Amstelveen, The Netherlands, with registered 
> number 33014286
> ********************************************************
********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************

Reply via email to