[David Barr]

Most of my replies to this thread are failing.

• This reply was modified 6 days, 1 hour ago by David Barr.
• This reply was modified 6 days, 1 hour ago by David Barr.

[David Barr]

You may be calling hcisetenv incorrectly. Here’s an example of a script that works:

#!/usr/bin/ksh
export CL_INSTALL_DIR=/opt/cloverleaf/cis2022.09
export HCIVERSION=2022.09
export HCIROOT=$CL_INSTALL_DIR/integrator
export FPATH=$HCIROOT/kshlib
setroot $HCIROOT
setsite live_ord_res
hcicmd -p cprof -c “cprof_out pstop”
hcicmd -p cprof -c “cprof_out_qa pstop”

[David Barr]

Which X server are you using? Are you using Exceed, Mobaxterm, AIX console, Xorg or something else? You could switching X server software.

[David Barr]

I’d keep troubleshooting. I don’t think HTTPS is the answer.

[David Barr]

I don’t think we have any HTTPS connections from Cloverleaf to Epic. We do have HL7 connections from Cloverleaf to HL7 listeners in Interconnect. Those are sometimes tricky to troubleshoot. You have to set up routing tables and point to them with the IC_IN_TABLE in system defaults. We have multiple levels of routing. The first table routes on message type and it points to other tables that route on either sending application or sending facility.

[David Barr]

How are you calling the TCL proc?

 

[David Barr]

That sounds very tricky. Normally that’s done with two pairs of threads: order_ib -> order_ob, result_ib -> result_ob. I wouldn’t recommend your pattern. Acknowledgements are going to be going over these interfaces as well, and it seems like they’re going to get mixed up with the messages.

[David Barr]

You can also add “-c” to your hcidbdump command if you want to see TCL errors.

[David Barr]

Is there a document with release notes for 2025.01? I found the release report which is an Excel document. Is there anything more readable? The spreadsheet doesn’t make it easy to find release highlights; you have to wade through descriptions of minor bug fixes, etc.

[David Barr]

If you run the IDE from Linux, the shell button opens up an Xterm window. If you’re using MobaXterm or other software that tunnels you GUI traffic over SSH, then it should be secure.

[David Barr]

We’re on Rackspace for our servers, so Cloverleaf is sort of running in a cloud, but not the Infor cloud.

David Barr (david_barr@valleymed.org)

 

[David Barr]

You can use \T\.

[David Barr]

You could always add a “msgdump $mh” command in your script for more debugging information. It should add messages to the process log to show you if the message has been modified, and if the msgdump output isn’t showing up it would indicate a problem getting your interface to run the script (not applied in the GUI or process not restarted).

[David Barr]

The code looks fine to me, and if the testing tool says that it works, then your actual interface is probably still running the old code. I think you can “reload procedure” through the gui to apply your change, but I always just restart the process where the proc is getting run.

[David Barr]

If you’re just decoding the base64 data and not passing it anywhere you may not need to remove the linefeeds. The decode will ignore them, and they shouldn’t affect your field lookups since they are using \r and | as delimiters. If you do want to remove the linefeeds, I think you could do something like this:
<pre>set msg [msgget $mh]
set msg [string map { \n “” } $msg]
set ctr_val [msgmetaget $mh “USERDATA”]
set segmentList [split $msg \r]</pre>

[Author]

Replies