Hi Eric, well, it depends. If you have a replication target server and there exists a CLOPTEST named windows, this shouldn't be overwritten by a node replication also using a cloptset named windows, at least to my opinion because the settings bundled in this clopset might be different. One might discuss the point of who is supposed to check that the cloptsets match and no harm will be done vs. "I know what I'm doing: replicate!!!!!", but that will be an endless discussion. If you want to supress the warning, delete the cloptset on the target side and let replication install it again. In the end, it's only a warning stating that there is a name conflict.
Regards, Michael Prix On Fri, 8 May 2020 09:23:51 +0000 "Loon, Eric van (ITOP NS) - KLM" <eric-van.l...@klm.com> wrote: > Hi Michael, > > If this is normal behavior, it shouldn't issue a warning message, do you > agree? For IBM: The whole process of configuring and using a server with > node replication is very poorly documented to my opinion. For instance, the > procedure to remove a node is drastically different for a replicated node > and you pretty much have to find that out yourself... > > 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 Michael > Prix Sent: donderdag 7 mei 2020 15:38 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: ANR1942W > > Hello Eric, > > the explanation to ANR1942W states that this is desired as normal > behaviour, if the CLOPTSET was already existing on the replication target. > There has been IT18951 stating the opposite for enterprise administration I > also observe this on servers who started replication between each other > after some time of operation. Some settings collide during the replication. > > Regards, > Michael Prix > > > On Thu, 7 May 2020 08:50:23 +0000 > "Loon, Eric van (ITOP NS) - KLM" <eric-van.l...@klm.com> wrote: > > > Hi everybody, > > > > We are implementing node replication on our new server and I noticed > > the following warning message in the log: > > > > ANR1942W Option set SPSERVERS already exists. Skipping for replication > > from source server AMSE3. > > > > All our servers are using standard naming, so option sets are all > > named identically on all our servers. Is that no longer allowed when > > using node replication? Thanks in advance for your help! > ******************************************************** > 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 > ********************************************************
