Adding context to Error DB msgs?

[Anonymous]

I know I can use”:

  msgerror context msgid

to place a message in the error DB with the context of my choosing, but this will not work if the message is “destroy-locked”.  Using the testing tool, the message always is destroy-locked, and I’m afraid this will be the case with any message that travels through the normal engine flow.  

I also know I can send a message to the Error DB with an:

  lappend dispList “ERROR $mh”

What I want, is to provide a little greater detail to why I am putting the message in the Error DB to begin with.  Every time I use this message the only context I see is “TPS ERROR disposition”.

Anyone know if I can change this context?  If not, I may resort to putting details in the msgmeta data, but I hate to do that if there is a better way.

Thanks in advance everyone!

Topic

[Michael Hertel]

I know it’s not what you want but we echo a message to the process log.

[James Cobane]

David,

You can set the USERDATA field to be valued to whatever additional text you want so that it is availabe.

[Charlie Bursell]

Not only can you add the error message using the USERDATA metadata field, it is a *MUST*.  I preach this over and over in any of my classes or presentations.

The ERROR continuation forces a Tcl error to send the message to the Error Database.  I can’t tell you how many times I have seen people spend hours and even days chasing a non-existent Tcl error when the message was purposely sent to the Error Database.

As for using msgerr vs the ERROR contiuation, I am in favor of always, if at all possible, sending messages to the error database prior to any translation, etc.

[Author]

Replies