Lisa,

I read your post as asking for some brainstorming on the kind of things that
will bite you on that fateful Monday morning.  If this were the case, and to
start the ball rolling, let me throw a few things out there, and others can
chime in.

- do your PCs find the 3000 using a hosts file, a resolved name or a fixed
IP in their logon scripts, and do you have a migration plan to check and
update them.
- do you have any jobs or scripts running which FTP to your 3000 with a
hardcoded IP in them.
- do you have a telnet listener job running to catch routed messages coming
through a pinhole in your router that would have to be changed, and if so
- do you have multiple 3000s talking to each other through DSLINE, and how
are they addressing each other.
- are you using your 3000 as a web server and if so how does your front end
find the 3000.

There are some real 3000 network gurus on this list and they may have some
more "hidden" potential problems, but this is start.  By the way, do you
have a crash and burn system that is similarly placed in your network
configuration (i.e. can be reached by the same types of connections) which
could have its IP and subnet changed to test your implementation of these
changes?

Hope this helps,
Rs~

Russ Smith
Systems Analyst, CalState9 CU, Concord CA, rsmith @ calstate9.comm
Programmer/Analyst, Problem Solved, Vacaville CA, rsmith @ cu-help.comm

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *