RE: Initiating a Windows DNS change from IBM i

Yes we run these scripts.

We have these so well documented that I can pass off the documentation to
non-admin IBM i developers and they can do the switch. And, as a test of
the documentation (and to ensure that if I or my backup get hit by the
truck...) I routinely pass these documents on to someone else and have
them run it. At times I have even left the state. Yes the boss gets a
little cranky and nervous about that so I don't make it a habit.
Especially the time I was at Scout camp with lousy reception.

For example
SCRIPT1 - Runs on main system (GDISYS1) to quiesce applications
SCRIPT2 - Runs on backup system (GDISYS2) to become main system.
perform dedicated processing on downed system. Might be able to be
scripted.
SCRIPT3 - Runs on downed system (GDISYS1). Done with dedicated processing
on downed system so start replication back up.
when you think it's all caught up replicating proceed. We normally wait
for Sunday evening to keep quiesce time consistent for operations.
SCRIPT4 - Runs on up system (GDISYS2). Quiesce "up" system and bring it
down.
SCRIPT5 - Runs the switch on the system that is going to become main
system(GDISYS1).
SCRIPT6 - Runs on up system (GDISYS1) to start replication.

All of these scripts have excellent restart capabilities. Sample
EDHSWIRUN SYSNAME(GDISYS1) SCENARIO(SCRIPT1) RUNMODE(*STEP) SEQ(0)
Says run SCRIPT1 and make sure I'm on GDISYS1. Since I said SEQ(0) start
at the beginning. If I wanted it to start at line 610 I could. And I've
done these kind of restarts. I just get in the habit of always specifying
the SEQ to help the "users" know they can.
RUNMODE(*STEP) says to stop at every line of the script and make me hit a
function key to proceed.
I can flag a line of the script as a comment. Often useful to comment out
commands you may put back in some time in the future.


Rob Berendt