|
Walden, Many many years ago (when I thought I knew SNA) I seem to recall being able to alias the AS/400 CP name via CRTCFGL TYPE(*APPNLCL). If memory serves me right (hint -- this means I have not tried this recently) you could change your Local control point name to your Current system name, and then create (or modify) the *APPNLCL Configuration List to specify your old Local control point name as a new Local Location name. This would allow you to use the current Client Access configurations with the old CP name to the newly renamed AS/400. I can no longer recall (age and all) whether you need to be a network node vs an end node (and that type of stuff), but perhaps others can help in that area. Bruce Vining > > 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 setting s on >this 400. My current problem is in the area of system names and networ k >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 CHGNET A >the network name. However, there are 50 some-odd PCs on the LAN that a ll >have SYSTEM1 as the remote machine name. So my question is: Can I chan ge >the network name on the 400, but assign an alias such that client acce ss >connections will work correctly regardless of what name the PC uses fo r >the 400, SYSTEM1 or ABC400? And, just in case that wasn't bad enoug h, >the 400 is also setup with a network name of AAA400 instead of APPN. A gain >a valid setup, but I want to change it to be APPN. Can I do this witho ut >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 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.