Re: Switching ID's -- MIDRANGE-L

I would suggest that there be some RISK ANALYSIS ... I think the odds ofsomething going seriously wrong with the 400 are small compared to the riskof the site being hit by disaster. Depending on your region of thecountry, and other factors, the risk will vary for what can come from badweather, earthquake, medical epidemic, criminal intruders, terrorism,insider misbehavior, vehicle crash into your building, etc.


When you think you have all bases covered, you need to schedule a TEST.
Either periodically thereafter, or after various upgrades, again TEST.

You may have package software that is licensed to SystemA CPUserial#. They may be willing to provide software key for SystemB at low cost.

Between time of last backup and the crisis, there may have been input workthat needs to be redone. Something to think about is paperwork flow suchthat you can reconstruct what was done since last backup.

Some package software keeps track of user input not by user-id but byworkstation-id


A PC can have more than one desktop icon for 400 access.
One for SystemA, another for SystemB,
which might want to use same workstation-id logic on both systems.

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.
--
        * Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
        615.995.7024
fax
        615.995.1201
email
        jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>