We are in the process of upgrading to 19.1.2.1 and are testing SMAT dB resends and found that when we select all (124,134) messages (through the GUI) we get the follow output

Command Issued:
hcicmd -p cc_enterprise -c “CC_DD_IN resend_db ib_pre_tps…Read more

What happened to patch 19.1.3.0

We have the release notes but the software is not available on the download site did they pull it back.

I have searched CloverTech and only found recommendations from 2013 are there more current recommendations since the Raima database were updated in version 6 of Cloverleaf.

How can I minimize the number of messages that are sent to the translation thread when I have multiple different criteria for different routes? If I have a Trx ID UPOC on the Inbound side that will create a subset of messages for the route as outlined in my above post which is based only on MSH then the only way to route any other messages…Read more

I have a simple question about message routing, in the NetConfig does each route defined create a sub process in a running engine.

For instance if you have an Inbound Trx ID Determination UPOC that prepends  data from the message route giving you a route such as (DMC|MMC|MIH|SHF)_ADT_A(0[1-8]|1[1-3]) with various route details an…Read more

Will the 20.x version of Cloverleaf be supported on Redhat Enterprise Linux 8.x

We found that when we converted from SMAT file’s to SMAT dB’s our disk space use was substantially increased.

The problem is that the sending application’s conversion process has bugs in it and they haven’t found them all yet. The code that we wrote works so I am not to concerned. The data is entered into a from and then converted to plain text.

Great idea the only problem is it is a known problem in the sending system and there is nobody on the application side to fix the issue. When you look at it on the application side it doesn’t look like there is a problem it only occurs when the system creates the HL7 message. Of course they told us 2 releases ago that it would be fixed…Read more

Thank you. The sending system randomly puts the r in the message and can be anywhere. Therefore we have to process the message in whole then put the r back in the correct locations.

We resolved the issue with the following in our script;
set newmsg [string map {“PID” “rPID”} $newmsg]
set newmsg [string map {“OBR” “rOBR”} $newmsg]
set…Read more

As it turns out this is a bug in 6.0.2 which manifests itself when you have a connection that is either up or opening and several hundred messages queued for that thread. The process panics and produces a core dump. This is what support had to say;

“R&D told me this was a bug that was reported and the fix will be in 6.0.3…Read more

I have changed 2 of the affected thread to use the TCP/IP with encapsulation, but have experienced no outages since the change.

Jim

It seems that when a thread is in an opening or up (but not connected) status and the queue depth is greater than 100 process panics. We have changed the engine output to enable_all and submitted the logs and core dumps to both McKesson and Infor. I have had no resolution yet, but still hoping they come up with some idea of what is wrong.

Jim

We tried recompiling the pdl to no avail the process panicked about an hour later. It only seems to crash when there are over 100 messages queued.

Thank you,
Jim

Not sure how windows works with IIS web services but on Linux when I did exactly what you mentioned I had to manually change the httpd configuration file to the new name/IP.

Jim

I currently provide management with the total number of inbound and outbound messages processed through Cloverleaf during the previous month. I also provide them with a historial chart of total inbound and outbound messages for the past 3 years at the end of the year.

Seeing these charts has allowed us to upgrade our servers and staff based…Read more