RE: Switching ID's -- MIDRANGE-L

Don't make things too hard on yourself.  Change the system name and the
network DNS address and be done with it.  If you have PC's with IAW host
files get them cleaned up and get rid of them.

You shouldn't even need to do the CHGNETA unless you are running native
SNA.  If you are using AnyNet you can just change the DNS entry for
SYSTEMA.APPN.SNA.IBM.COM to point to the IP address of SYSTEMB.

We did an application migration a couple of years ago and we have about
150 people with NetServer mapped drives.  All we did was change the
NetServer name and the DNS entries and everyone came up on Monday.  To
be fair I had spent a couple of years previous to this getting the
desktop guys to get rid of the individual PC host files.

P.S.  Don't forget: Part of your D/R plan should be testing your D/R
plan!

Regards,
 
Scott Ingvaldson
iSeries System Administrator
GuideOne Insurance Group


-----Original Message-----
date: Mon, 16 Oct 2006 09:03:08 -0500
from: Jerry Adams <jerry@xxxxxxxxxxxxxxx>
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.