Well, if you are certain that your trapd.conf definition is correct, and it seems to be from what you said, then the only explanation I can think of is that for some reason the updated trapd.conf was not loaded. When you exit the GUI, a FMTCHG event is supposed to be sent to trapd so that he knows to load the new file. You can duplicate that at any time by issuing
event -e FMTCHG
In the trapd.log (because it is a Log Only event) you should see a message that the format has changed.
After that your new trap should format correctly, according to what you defined.
If you see a message in the trapd.log after you issue the FMTCHG event that there is a problem with the trapd.conf file, you'll have to fix that and repeat the process.

James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group