Now, with Cloverleaf 6.0, it looks like this:
$ hcidbdump -e -c
C
l T
a y F
s p w
Created Message Id s e d Prio State Length Source Dest
——– ————– – – – —- —– —— ————— —————
16:44:50 [0.0.89275] E D N 5120 302 1776 tba8do__i to_sph_inv
‘Tcl error:
msgId = message0
proc = ‘NH_AuditLogi…’ error in ‘XLATE NH_SMS__ADT__NH_AuditLogix.xlt’ under ‘ADT_A08’ to ‘to_sph_inv’;
Previous recovery db state is 5.
This doesn’t even display the full name of the proc that cause the error. If you have multiple procs named similarly, you wouldn’t know which one caused the error given this information.
Is there any way to make it display the entire Tcl error stack like before? It was so much easier to just see the errors here than figuring out which process the thread is in, then searching the entire process log for the error.
Thanks,
Troy Morton
Interface Developer
Novant Health