Re: [nv-l] Location.conf

[Leslie Clark <lclark@us.ibm.com>]

Look what I found in my file folder 'code problems'. Hendrik told us about this fix a month ago. The archives are a great backup for a failing memory, if you can remember to look there....

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
----- Forwarded by Leslie Clark/Southfield/IBM on 02/19/2004 07:54 AM -----

"Hendrik Zahn" <hendrik.zahn@de.ibm.com> Sent by: owner-nv-l@lists.us.ibm.com 01/20/2004 02:15 AM Please respond to nv-l

To:        nv-l@lists.us.ibm.com         cc:        nv-l@lists.us.ibm.com, owner-nv-l@lists.us.ibm.com         Subject:        Re: [nv-l] lcoation.conf 7.1.4

Hi Christopher,
my experience is that it doesn't matter which location symbol is used as
parrent and which is used as child.

I guess that your location.log contains still some more errors e.g. that OH
couldn't be created because it already exists.
Furthermore I guess that you get the problem when you openes a new
additional map.

All this sounds for me like APAR IY48698 which is fixed with NV713 FP02 and
in all furtehr releases like NV714 FP01 (which isn't available yet).
But you can get an interim fix for IY48698 from your support team.

Maybe this helps you.

Regards,
Hendrik




                                                                                                                                                    
                      "Christopher J                                                                                                                
                      Petrina"                 To:       nv-l@lists.us.ibm.com                                                                      
                      <cjp8@meadwestvac        cc:                                                                                                  
                      o.com>                   Subject:  [nv-l] lcoation.conf 7.1.4                                                                 
                      Sent by:                                                                                                                      
                      owner-nv-l@lists.                                                                                                             
                      us.ibm.com                                                                                                                    
                                                                                                                                                    
                                                                                                                                                    
                      20.01.04 00:14                                                                                                                
                      Please respond to                                                                                                             
                      nv-l                                                                                                                          
                                                                                                                                                    
                                                                                                                                                    





here is a small example of my location.conf

MidWest 0 Site
OH 0 Site MidWest
KY 0 Site MidWest
IN 0 Site MidWest
WV 0 Site MidWest

Dayton 10.x.x.x Site OH
Dayton 10.x.x.x. Site OH
Dayton 10.x.x.x Site OH


OK that seems simple enough right?  Should create a container in OH called
Dayton.   Since OH is already defined in MidWest.

I keep receiving the following error though.

location.conf[409]: Dayton 10.x.x.x Site OH
     Unknown parent location: 'OH', parent entry must occur before child

any ideas.

Chris Petrina