× 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: Neil Palmer <npalmer@xxxxxxxxxxx>
  • Date: Wed, 17 Dec 1997 13:44:15 -0600

Walden,

Short answer - NO.
(By 'Network attribute for system name' are you referring to the 'Local
control point name', 'Default local location' or both ?).

As you're probably aware the default setup for AS/400 network attributes
is to have SYSNAME, LCLCPNAME & LCLLOCNAME all the same (default being
'S' plus the serial number but of course that's the first thing
youchange when you get a new machine, right !  :-) ), and to have a
LCLNETID of 'APPN'.  The AS/400 does have a place you can store an
alternate system name - it's the 'Secondary system name table'
(CFGDSTSRV, option 3).  However, as far as I know there is no ability
for a secondary or alias Network Id.

It's possible you may be able to manually change all the APPC
controller/device descriptions for every PC (changing RMTNETID on the
controller, and LCLLOCNAME & RMTNETID on the devices), but then you'd
have to forget about using auto-config to create any more devices.

I'd recommend biting the bullet and going around to all 50+ of those
PC's one weekend and changing the AS/400's Network ID and Name in all
the setups.


... Neil Palmer                                     AS/400~~~~~      
... NxTrend Technology - Canada     ____________          ___  ~     
... Thornhill, Ontario,  Canada     |OOOOOOOOOO| ________  o|__||=   
... Phone: (905) 731-9000  x238     |__________|_|______|_|______)   
... Cell.: (416) 565-1682  x238      oo      oo   oo  oo   OOOo=o\   
... Fax:   (905) 731-9202         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
... mailto:NPalmer@NxTrend.com          http://www.NxTrend.com


        -----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

        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 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.