Subject: Re: What stops working when CHGRDBDIRE is used? From: rob@xxxxxxxxx Date: Thu, 13 Mar 2014 10:38:08 -0400 List-archive: List-help: List-id: Midrange Systems Technical Discussion List-post: List-subscribe: , List-unsubscribe: ,

form. When you've swapped that out 3 times and it's on it's third serial
number it hardly makes sense. Or when you have multiple partitions and
having S123451, S123452, S123453, S123454 for the various partitions also
doesn't make sense. We've long outgrown our system names of BERT and
ERNIE. And the IBM rep practically yanked the keyboard out of my hands
when I almost named our first AS/400 SNUFFY and make it GDIHQ. We still
have GDIHQ 20+years later, through many serial number changes.

Changing the system name:

BRMS:
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/brms/sc415345233.htm

Do a DSPNETA. Record the values for:
Current system name . . . . . . . . . . . . . . : GDISYS
Pending system name . . . . . . . . . . . . . :
Local network ID . . . . . . . . . . . . . . . . : GDI1
Local control point name . . . . . . . . . . . . : GDISYS
Default local location . . . . . . . . . . . . . : GDISYS
...
Network server domain . . . . . . . . . . . . . : GDISYS

Prompt CHGNETA. Set those appropriately.

CFGTCP
12. Change TCP/IP domain information
10. Work with TCP/IP host table entries

Hopefully you aren't working still with anything in CFGDSTSRV that should
concern you. (SNA stuff).

There are ways to have WRKRDBDIRE support two local system names. This is
normally a concern for High Availability machines. For example, let's say
you have GDIHQ1 and GDIHQ2. They both can be GDIHQ. Not at the same time
normally but after a H/A switch. So all the users just always connect to
GDIHQ. But sometimes a systems person needs to specify GDIHQ1 or GDIHQ2
to query some stuff to see if we're ready for a switch. I could tell you
how to do this to patch your system to support both the old, and the new
name, but I'll think I'll hold that one close to the belt so you get your