"Westphal, Raymond" <RWestphal AT erac DOT com> writes:
> OK - I admit it; I don't get this trapgend thing. I'm confused about the
> conversion of the "hex error ids". I wrote a little Perl script to convert
> the AIX hex error ids to decimal. Here's the output. AIX error ID on the
> left is converted to the hex on the right. (I attached the label for
> reference.) The hex calculator on Windows agrees with results. However, the
> xnmtrap screen shows an existing OPMSG entry with -1433750975. 

The first bit of AA8AB241  is a 1, indicating a negative number if
dealing with signed, 2's complement integers.   The rest are positive
numbers in either signed or unsigned integer coding. 

Sounds like whatever translation happeneing in xnmtrap is using signed
arithmetic.   If that's not the right thing to do, this would warrant
a chat with support to log it as a defect. 

> AA8AB241 = 2861216321 (OPMSG)
> 4EE9D892 = 1323948178 (PHXENT_DOWN)
> 54E423ED = 1424237549 (SCSI_ERR9)
> 56CDC3C8 = 1456325576 (MACHINE_CHECK_CHRP)
> 5DFED6F1 = 1576982257 (JFS_FS_FRAGMENTED)
> 627A4F55 = 1652182869 (BADISK_ERR3)
> 684A365B = 1749694043 (JFS_META_CORRUPTION)
> 
> Will my rulesets work with my decimal values?

-- 
Todd H.
http://www.toddh.net/