MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » November 2006

RE: System name



fixed

And as a follow-up, my general rule when setting up new replication
environments is that anything in the IFS is *EXCLUDE unless you have a
proven requirement that it's needed.  Lots of trouble to be had in
IFS-land.  Especially in directories with OS400 in the name.  Glad it
was a relatively easy fix.


--
Justin C. Haase - iSeries System Engineer
IBM Certified Systems Expert - System i
Kingland Systems Corporation

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Haase, Justin C.
Sent: Monday, November 13, 2006 4:07 PM
To: Midrange Systems Technical Discussion
Subject: RE: System name

This particular file sounds like user or vendor error, not a DCR
opportunity. 


--
Justin C. Haase - iSeries System Engineer IBM Certified Systems Expert -
System i Kingland Systems Corporation

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, November 13, 2006 3:42 PM
To: Midrange Systems Technical Discussion
Subject: Re: System name

I think I figured this out.  I believe there is a load of IFS files that
IBM likes to store a bunch of rot into.  Well, as part of a Mimix
implementation we restored a few too many IFS files from our production
lpar to our Mimix lpar.  I just found a little file that was obscuring
my Management Central connection.
/QIBM/UserData/OS400/MGTC/config/McEPConfig.properties
Alas, they do not put this on the properties screen for management
Central like they do for NetServer.  Time for a Design Change Request
perhaps?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/10/2006 01:20 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
System name






New lpar.  I verified:
- CHGNETA
- CHGTCPDMN
- CFGTCP
  1. Work with TCP/IP interfaces
  10. Work with TCP/IP host table entries
However, when I fired up NetServer it still said that it was the name of

this existing lpar.  Granted it was only 1 character off and I could
have 
fat fingered something.  And, it was no big deal to modify the NetServer

properties to use the right one after the next start of NetServer.  My
big 

concern was where did it get that name originally?  I'd hate to thing of

something else that might think it is the wrong system.

Rob Berendt





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact