RE: Switching ID's

["Jonathan Mason" <jonathan.mason@xxxxxxxxxxxxxxxx>]

You would have to change the IP address of SystemB to match that of SystemA.
This would be done via GO CFGTCP where you can use option 1 to work with
Interfaces (Network Cards effectively).

At one company I worked for, however, the Windows Network Logon script was
coded so that it would automatically copy files from a network folder to a
local folder if required.  When we moved offices and had to update around
200 PCs running Client Access we used this mechanism to copy a new Windows
Hosts file to the PC.  We also wrote in to our DR procedures to use the same
mechanism to update Client Access during a disaster.

Jonathan

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: 16 October 2006 15:03
To: Midrange-L
Subject: Switching ID's

We have two [2] 520's.  One is production; the other is our backup system.
Both are single partition.  There are 20 - 30 workstations and about the
same number of printers.  The workstations are primarily PC's using iSeries
Access for Windows; we have a few twinax workstations (including the system
console).


So far we (knock on wood) haven't had to use the backup system for
production.  Someone had the radical idea, however, that we actually needed
a disaster recovery plan.  I need a little (?) help with an aspect of the
plan.


For this phase we are assuming that the damage is isolated to the production
box (SystemA); that there is no structural damage to the environs; that
everything else is copasetic.  I port the configuration from SystemA to
SystemB (the backup) in a save file (SAVCFG) automatically every night.
(Forget to mention: Both boxes are supposed to be identical in all regards.)
Security data (SAVSECDTA) is, also, pushed to the backup in a save file.


My question relates to user access via iSeries Access for Windows.  Each PC
user's IAW is configured to identify SystemA as the system to which they
will access programs and data.  Even though there are "only" about 20 PC's
attached this way, I would rather not set up a connection to SystemB and,
then, change each PC to access the backup system.  Instead, I would rather
change the identifier on the system (520) itself.


It looks like CHGNETA can be used to rename the systems.  Is this all that I
need to do?  Or do I, also, need to change the IP address for the box?  I
seem to remember that there is a server somewhere that says, "IP address
10.0.0.4 = SystemB" etc.  Is that the Domain Name Server (DNS)?  
And would I need to change that, too?


Thanks.