Thanks, Pat, for the response. Here's what testing told me. Apparently the hardware configuration area is one of the all-or-nothing sections where the OBEYFILE replaces everything that TCPIP already was using.
Feeding my original OBEYFILE into TCPIP caused me to lose both my ports. I also lost all my route information, including defaults. Once I added all the DEVICE, LINK, HOME, and ROUTE information for both my ports to the OBEYFILE, I was able to successfully activate a new IP address on one of the ports. Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Patrick O'Keefe Sent: Friday, January 12, 2007 3:04 PM To: [email protected] Subject: Re: Simple TCPIP OBEYFILE question On Fri, 12 Jan 2007 10:34:23 -0600, Pommier, Rex R. <[EMAIL PROTECTED]> wrote: >... >I have an OBEYFILE that looks like this: > >DEVICE GIGADEV0 MPCIPA >LINK GIGA00 IPAQENET GIGADEV0 >HOME > 172.16.0.7 GIGA00 >START GIGADEV0 > >This OBEYFILE only contains the configuration information for the port >I want to change. I should be able to feed this OBEYFILE into TCPIP >and get the IP address changed without impacting the other OSA port, right? No. You are right about Device and Link defs. You have to do a DELETE to get rid of them. But a HOME statement resets the Home list. You have to add all static Home definitions. (Entries that were added dynamically - DVIPAs, dynamic XCF links, etc. - will be dynamically readded.) >... Also, do I need to feed the >BEGINROUTES/ENDROUTES block into the OBEYFILE since that isn't changing >either? >... I think you are safe with BEGINROUTES/ENDROUTES, but we use dynamic routes and don't use BEGINROUTES/ENDROUTES so I'm not absolutely sure. Pat O'Keefe ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
