I had same issue with 5.0 to 5.1 upgrade.  Tivoli support said that script
was looking for too long of entries.  I used vi to edit
/usr/OV/conf/C/trapd.conf file.  You need to leave the SDESC header, but I
removed the options pieces of those statements.  Example
SDESC
This trap is generated when the long tem link
error rate, fddimibPORTLerEstimate, crosses the
fddimibPORTLerAlarm threshold.  The variables are
found in IETF FDDI MIB RFC-1512.

There were some lines that followed this, so I deleted them.  I left the
next EDESC header in place and reran the check script.

db







"Radcliffe Jr, Arthur W" <arthur.radcliffe AT AETNA DOT COM> on 03/11/99 
11:14:15
AM

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: David S. Barrett)
Subject:  Netview 4 to 5.1 Upgrade  chktrapd.con script




Hello all,

While doing a Netview Version 4 to 5.1 upgrade, I ran the chktrapd.con
script, and received a number of errors stating that the length of the
Description field of traps, was greater than 99 words.  I was wondering
why
the script would check for that,  why the length of the Description field
is
an issue to Netview 5.1 and whether we need to do anything to those
description fields.