$ hcitcptest -t mlp -h qted -p 5309
Data recieved from the host will be printed to standard
output in a hex dump format. (Including any encoding chars,
data is dumped exactly as read.)

If you wish to…Read more

for the stats it sounds like the hcimsitutil command would have the info you want. hcimsiutil -dd threadName will give you a bunch of information about thread activity.  there are also tcl commands (msiAttach, msiTocEntry, msiGetStatSample) that you can use to get a keyed list of the thread statistics that appear in the hcimsiutil…Read more

I think you can infer from the line feed in the “unknown segment” messages (the 3 chars between the ‘ ‘s ) that in the bad message there is a line feed char after each segment delimiter. That out of order segment message takes the first 3 chars after the segment delimiter as the next “segment header” (as it should)

Turning up the…Read more

If I read your second post right, you want to exec a SUPPRESS when PV1:10 is NOT one of {OBS,NRY,OOB,OBV}  so you want to “AND” (&&) and not OR (||) your individual “ne” conditions in the original “IF” statement like this:

IF   0(0).PV1(0).#10(0)  ne =OBS &&  0(0).PV1(0).#10(0)  ne =NRY &&  0(0).PV1(0).#10(0)  ne =OOB &&…Read more

if you search for “inrecoverable socket error” there are different ways that the monitor…Read more

I wasn’t able to open the doc but the proc is not yet available because

Our IDN recently went live with Soarian on 9/15. We did not purchase openlink, so I can attest to some of the issues encountered receiving HL7 2.X ADT with about 30 downstream systems.  

1) Dynamic Delimiters. This one was my pet peeve. Soarian HL7 has an unusual approach to the implementation of characters that would otherwise be…Read more

I’m presuming you’re on some unix variant based on your path – we’re on AIX.

We once hit the process status limit on the “hci” user and had problems logging in although that was not the exact error message we saw – we got some fork failure most of the time.  

root cause for us was that some OS setting that limited the number of PIDs…Read more

check and see if your OS tcp “keepalive” setting is longer than the  firewall’s “session timeout”. (Or the shortest session timeout if there are firewalls on both ends) If the firewall times out the session that could collapse the tunnel in such a way that one side still thinks they are connectd.  

If the other side sees an “up”…Read more

check and see if your OS tcp keepalive setting is longer than the firewall’s “session timeout”.  

We had a situation where the firewall (Fortigate or Fortinet) changed their “system session time” from 60 minutes to 5 – our networks group did this due to some concerns about a memory or handle resource issue. Our CL box had the tcp…Read more

we had an XLT file with an incomplete condition line in an IF.

   { COND { 0(0).MSH.#9.[1] eq =A02 &&  1(0).1(0).PV1.#10  eq  } }
should have had a value tot he right of the a second eq.

hcixlttest on just the xlt file didn’t indicate any syntax error/failure to load, although once a message occurred (or was…Read more

PANIC: assertion ‘vs != ((struct ValueStack *) 0) && val != ((struct Value *) 0) && (val)->val_next == ((struct Value *) 0)’ failed at Value.cpp/958

search on the assertion that failed (“assertion ‘0’ failed at PthreadInterface.cpp/699”). “PthreadInterface and 699” gets about 5 hits. I can’t tell you exactly what causes the initial panic but stopping the site and restarting cleared it up for us once.

our environment is CL 5.5 on AIX 5.3

We’ve had similar issues on 2 of our VPN connections. (never on a non-VPN socket)

In our case the read error was a slightly different number (our threads are using r/t TCP-IP HL7 MLP). Also, our errors would not stop until our log files would hit the max unix file size and the engine process…Read more

Whenever its possible to select no rows in your fetch you have to initialize all your bound variables first.

The SQLBindCol function will associate a column with a variable name but if the data set resulting from your SQL fetch is empty  (or you don’t actually call SQLFetch) then the bound variables won’t get set in the fetch. In other…Read more

set newMsg [ string map { ”  ‘ } $msgData ]

Since the warning is saying that the #2 segment is the PV1 it looks like the root cause of the warnings is that you are receiving some messages where an MSH is followed by a PV1 instead of a PID segment.

We used 5.3 on AIX to connect to SQL server 2005 so hopefully that is close enough. We bought the odbc Data Direct add-on from cloverleaf.

The MS-SQL driver file (that goes with version 8.0 of the odbc package and MSSQL 2005) we use is CVmsss22.so and on our site installed to  $HCIROOT/lib/Connect5.2/lib.

The MS SQL driver files…Read more

possible gotchas to not keeping the outbound SMATs

If any of your XLTs or TPS procs depend upon tables that change, you may have some latency issues. Replaying an old set of inbound data through a newer route/TCL/table/Xlate configuration might not exactly replicate what did in fact happen.

There’s also the hassle of re-playing…Read more

hcixlttest at the command line will generally give a fair amount of detail on the offending statement (I think this is just what “compile” runs in the GUI.)

Here’s what I got when I deliberately mangled a table name in a working xlt.

$ hcixlttest temp.xlt
[0:TEST] Unable to load TBL ‘asdasddhinChartNames.tbl’
[0:TEST] Cannot resolve…Read more

We see similar chronic “hanging” problems. In our case the root cause is some design issues with the remote database.  Our stored proc “exec” gets deadlocked / blocked in the remote database and never returns.  We know this because we have echos immedaitely prior and after the SQLExecDirect call. While the SQLExecDirect call is hung…Read more

I see a different default on our box so I wouldn’t give up.

we run 5.5 on AIX, and the “output selection” file that activates when you select “file” instead of “screen” defaults to the “$HCIROOT” direcectory – in our case /hci/qdx5.5/integrator. We could create a common dir under that somewhere.

Also, you can manually navigate around the…Read more

One way (not sure it it is the only way or not) to make this happen is for 2 processes to both be using the same user ID to access the database at the same time. The second process trying to use hcidbdump on the user ID will get locked out with that as the error message.

If you call hcidbdump but don’t specify a user ID with the -U…Read more

If there are no required fields in the segment you can set up an iterate on the segment(s).

If the segment isn’t there on the inbound message you shouldn’t enter the iterate loop. Your basis won’t be a list, it will probably be group or segment – the specifics will depend on your message definition.