|
That is sarcasm, isn't it?
It's best to follow the examples in the manual and not use the flexibility of the operating system.
-------- Original Message -------- Subject: Re: Change system name From: Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx> Date: Tue, April 26, 2005 8:53 am To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
My opinion is that configuring your system the way others expect it to be configured makes it more workable. Just because IBM gives us more than enough rope to hang ourselves, there's no reason to do it.
If the way you configure your system causes IBM to have to spend more time on your support call, then you (or we will all) will ultimately pay the price for it.
Al
Al Barsa, Jr. Barsa Consulting Group, LLC
400>390
"i" comes before "p", "x" and "z" e gads
Our system's had more names than Elizabeth Taylor!
914-251-1234 914-251-9406 fax
http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com
PaulMmn <PaulMmn@xxxxxxxx m.com> To Sent by: midrange-l@xxxxxxxxxxxx midrange-l-bounce cc s@xxxxxxxxxxxx Subject Re: Change system name 04/25/2005 10:12 PM Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com>
I want to point out that although it's "traditional" to make the SYSNAME, LCLCPNAME, and LCLLOCNAME the same, strictly speaking it's not required. I'm not sure about NWSDOMAIN.
However, the fun and games you will encounter if S,L, & L don't match are not worth the effort of making them different. Ask me how I know!! (:
Example: IBM help line: "OK, now SYSNAME and LCLCPNAME are the same, so...." Us: "Uh, no, they're different." IBM: "They're different??!!?? They're supposed to be the same." Us: "No, they are just -usually- the same." IBM: --silence-- Us: "Hello??" IBM: "Uh, hold on a minute-- I need to check with someone else...."
--Paul E Musselman PaulMmn@xxxxxxxxxxxxxxxxxxxx
CHGNETA SYSNAME(new-name) LCLCPNAME(same-name) + LCLLOCNAME(same-name) NWSDOMAIN(same-name)
You must then re-ipl.
Al
Al Barsa, Jr. Barsa Consulting Group, LLC
-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.