× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Changing System Name
  • From: Bob Crothers <bcrothers@xxxxxxxxxxxxx>
  • Date: Wed, 17 Dec 1997 12:15:50 -0000

What system value are you talking about with the system name in 
it?  There is none.  The system name is set in the Network 
Attributes.  Change with CHGNETA, view with DSPNETA.

You are probably thinking of the Serial Number (QSRLNBR).  This 
is a serial number, not the system name.  When OS/400 is 
installed, the system name defaults to an "S" followed by the 
serial number.

You should never assume that the system name is the serial 
number or that the serial number is the system name.  What 
happens if they change serial numbers?  Then you would want to 
keep the system name the same or else you would have to change 
all the PC's and any other APPC system that talk to you.

The better way is to change the System name to something that 
does NOT look like a serial number.  Like maybe SYSTEM1.

Also, there is nothing wrong with changing the Local Network ID 
from APPN to something else.  If you might ever link with 
Advantis, you should set it to IBMIN because that is what they 
insist on. Otherwise, I'd leave it at APPN.  But, it can be 
anything.

Bottom line is I think that your customer has done the correct 
thing.  Whether by accident or intent does not matter.  The 
system name is the first thing I change on a brand new box.

As to changing the System Name without effecting your PCS and 
CAWin machines, I don't  think you can do it.  It is possible to 
have the remote network ID different from the local network ID, 
but it is a pain and I would not do it without a good reason.

Keep in mind that the above is all MY opinion and I could be in 
left field.  Part of the beauty of the AS/400 is it's 
flexability.  But that gives you a million ways to do something. 
 Many of which are "right".

Regards,
Bob Crothers
Cornerstone Communications




-----Original Message-----
From:   Walden Leverich [SMTP:walden@techsoftinc.com]
Sent:   Wednesday, December 17, 1997 7:15 AM
To:     Midrange Mailing List (E-mail)
Subject:        Changing System Name

 << File: ATT00000.htm >> I've stumbled into an account where 
the AS/400 was setup by people that don't know the 400. I'm now 
looking at fixing some of the settings on this 400. My current 
problem is in the area of system names and network names.

The system value for the system name contains 'ABC400' (Well, 
not really, but the names have been changed...) and the network 
attribute for system name contains 'SYSTEM1'. While I know this 
is technically valid I would like to change the network name to 
bring it into sync with the system name (I want them both to be 
ABC400). No big deal, I can CHGNETA the network name. However, 
there are 50 some-odd PCs on the LAN that all have SYSTEM1 as 
the remote machine name. So my question is: Can I change the 
network name on the 400, but assign an alias such that client 
access connections will work correctly regardless of what name 
the PC uses for the 400, SYSTEM1 or ABC400?

And, just in case that wasn't bad enough, the 400 is also setup 
with a network name of AAA400 instead of APPN. Again a valid 
setup, but I want to change it to be APPN. Can I do this without 
effecting all the PCs?

Any help would be appreciated.

-Walden

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.