Re: nvaddtrapdconf failure
The nvaddtrapdconf script uses awk to parse the incoming file, and
trapd.conf, and the kicker is that awk has a limit of 99 arguments. This
is not a problem until you get to the trapd description. Many vendors are
very wordy. If the description contains more than 99 separate words, then
the awk fails, and so does the script.
All you can do at this point is edit the input file and see if you can cut
down the offending descriptions(s).
PS: <soapbox on>
For what is worth, I much prefer REXX myself, but most UNIX systems are
still wedded to the dark ages. It's some kind of rite of initiation that
one has to learn vi, shell script, awk and sed; and many UNIX folks are
proud that they have mastered these rather esoteric tools. So they never
get changed or replaced. I think it is humorous that such a big deal is
made about the portability of C / C++ code to platforms other than UNIX
and no attention is paid to the fact that REXX is a completely portable
script language. You'll just have to grin and bear it Ken. <soapbox off>
Tivoli (NetView for UNIX) L3 Support
"Ken Freeman, Woolwich plc" <GBWBSJHS AT IBMMAIL DOT COM> on 10/22/98 06:29:26
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L AT UCSBVM.UCSB DOT EDU>
To: NV-L AT UCSBVM.UCSB DOT EDU
cc: (bcc: James Shanks)
Subject: nvaddtrapdconf failure
Once again I am working on the thorny topic of adding definitions of
traps to my trapd.conf file.
I have received some details from Microsoft on how to create a list of NT
events that are being translated to traps and from these details I have
able to create a series of files to add using the nvaddtrapdconf command.
Whilst this processing has been relatively successful I have a couple of
files that fail to merge. The message produced by the failures is as
# nvaddtrapdconf MicrosoftDNS.traps
awk: 0602-535 Line Microsoft Origin - $ cannot have more than 99 fields.
The source line number is 57.
ERROR: unable to merge files.
The source line number is always 57 but I am not sure if this relates to
trap definition file or the nvaddtrapconf script.
I have browsed the nvaddtrapdconf script but I am unable to make any sense
it (I usually use REXX and do not understand AIX scripts).
Can anyone shed any light on what is occurring?
I don't think that the trap definition files are at fault as they are built
using the same REXX exec as those that are successfully merged.
Thanks for any assistance,
Ken Freeman <gbwbsjhs AT ibmmail DOT com>
BTW - I am happy to provide the instructions we received from Microsoft if
anyone else needs to create definition file(s) for NT traps.