xpmerror curdetail

Last week we discovered a problem with the “xpmerror curdetail” command.  We have an Xlate action that calls a TCL procedure to look up a regional doctor number.  On certain error conditions, the following line of code is executed:

   xpmerror $xlateId curdetail $ErrMsg

to error out the current route detail but continue with the rest.  What we discovered was that an error message was written to the process log:

   [xlt :xlat:ERR /0:uah_tst_xlate] [0.0.21140094] Xlate ‘UAH_A08O_META_ADT.xlt’ failed: Regional doctor number not found for UAH-990162.

but the message did not go into the error database.  Both the inbound and the erroring outbound threads are using recovery database.

If we changed the xpmerror command to use “alldetail”, it wrote the same error message to the process log AND it sent the message to the error database.  As expected, no other receiving outbound threads got the message.  So, the “alldetail” argument works as expected but the “curdetail” doesn’t.  We think “curdetail” should have also sent the message to the error database.

Has anyone encountered a similar problem with “xpmerror curdetail”?  Could this be a bug?  We are running release 5.3 Rev 2 on AIX 5.