|
Thanks for all your suggestions Bill, I'll try some
of them monday when I'll go to the client.
I think I forgot to say I'm on redhat
Linux.
Also I would like to add some comments to some of
your suggestion in order to clarify the problem (or maybe to complicate
it):
1. I will try to create a new location.conf file
from scratch but anyway I don't think I have problems with the
header
2. initially it was Brauunion 0 Site but after
the problems started I've tried some variants like 255 or 1-255. Also I
forgot to say that sometimes the Brauunion location is created and sometimes it
evens contains one child location, but the errors are still there! I
think that's quite strange!!
3. I also tried this one ... nothing!!
4. I'll try this one..
What about the APAR IY48698 ??
Sincerely Yours / al Dvs.
Lucian Vanghele,
Senior System Engineer,
Business Information Systems- BIS srl
tf./fax:+4021 255 4579
----- Original Message -----
Sent: Friday, June 11, 2004 6:45 PM
Subject: Re: [nv-l] again
location.conf
This is old stuff so we shouldn't see any
problems with this area. All those messages point back to a problem in
recognizing the first entry in the list.
location.conf[109]:
: Too few fields - missing address
pattern.
location.conf[110]: Militari 255 Site
Brauunion
Unknown parent location:
'Brauunion
Somehow the address field of the "Brauunion"
primary entry is not recognized as a valid address. I've not used the
255 notation myself since I haven't created any location.conf files since I
recently learned you can use anything but zero as a place holding
address. Suggestion 1. Make sure your file header
isn't creating any problems.
Suggestion 2. Try "Brauunion 0 Site" as the
first entry then something like "Militari 0 Site Brauunion" for each
sub-location. "255" should work as well as "0" but I can't personally
vouch for that. This is the keystone of the location structure.
It's the part which is not being accepted at the moment. There may even be
some non-visible character on the line separating the fields instead of true
spaces. You may also try something like 255.255.255 as a placeholder
address. One little line is causing all the problems.
Suggestion 3. Group all the subsites up top
with the main site. Then test it without all the individual
entries. The empty location submaps should be created anyway.
Suggestion 4. You can save a lot of effort
if you leave the "Icon Parent" off every entry after the first one for each
location. It also eliminates two opportunities for error on each
individual line where the site or parent link don't match in all cases.
(Yes, I've made that error.)
----- Original Message -----
Sent: Friday, June 11, 2004 10:05
AM
Subject: [nv-l] again
location.conf
I try to use location.conf but I receive lots of
errors in location.log
starting with:
too few fields - missing address
pattern
militari 255 Site Brauunion
Unknown parent location:
'Brauunion', parent entry must occur before
child
....
and so
on
I read something about an APAR but I saw it was for 7.1.3 and
solved
for 7.1.4..
what's wrong then?
the content of
location.conf is someting like that:
Brauunion 255 Site
Militari 255
Site Brauunion
location.log is like
that:
|