[Mike Keys]

Bob,

It should work just fine, BUT you need the images from one of the files that match your environment to the clgui.jar file.

[Mike Keys]

Just found Rob Abbott’s mlp_tcp-showMatch.pld script. Found that the client is sending back ACK with errant character in the message wrapper. Ticket opened with client.

[Mike Keys]

No, these are real time.

[Mike Keys]

Yes, I am trying out one called PDFCreator, but there are some issues…namely truncating of the filename, which has resulted in a rather complex setup.

We are also exploring getting encapsulated PDFs out of our EHR so we can decode into a filename for processing by a homegrown app which makes API calls to an ancillary EMR. I would prefer us to go this route.

[Mike Keys]

Jim,

Thanks! With your help, this is now working as expected!

Mike

[Mike Keys]

David,

o.k. thanks. Done and still works fine.

Mike

[Mike Keys]

Charlie,

Thanks. I grabbed the latest version of pdf4tcl and when running a message against it found that it requires Tcl version 10.0. I had to go back a version that still supported Tcl 8.4/8.5 and the package works fine.

It works fine living in the directory under  $HCIROOT/tcl/lib/tcllib-1.16

Mike

[Mike Keys]

Mark,

Funny you mention pdf4tcl, as that’s what I’ve been playing around with today and finally got to work.

Mike

[Mike Keys]

So, found out that when using Cloverleaf 5.7 this isn’t an issue. Testing in this environment with the string map function works as expected.

What I had to eventually do was change the encoding on the outbound thread to ISO-8859-1 in conjunction with the string map call.

I opened a ticket with Infor and this was what they said:

“Beginning with 5.8 we merged the regular cloverleaf with the multi-byte cloverleaf which is probably why you see the difference and need to specify the encoding for it to handle properly.”

[Mike Keys]

Jim,

Just in a certain segment? Throughout entire message?

I’d be inclined to write a Tcl pre-proc that would loop through each segment and remove those, since you build the output buffer and can put the r back on the end of the segment.

You’d have to ensure the r is the last character in the segment when splitting the message.

Mike

[Mike Keys]

What is Error code 26?

smat:RMI TCP Connection(74509)-10.8.121.130: ERR: 02/21/2017 11:49:36: Failed to attach /hci/cis6.1/integrator/adt_prod/exec/processes/REG/SmatHistory/EMR_IA_REG.20170221105042.smatdb with conn -1733907592

smat:RMI TCP Connection(74509)-10.8.121.130: ERR: 02/21/2017 11:49:36: Error code 26 returned.

smat:RMI TCP Connection(74509)-10.8.121.130: ERR: 02/21/2017 11:49:36: File being opened does not appear to be an SQLite database file. Enctypiton key might be incorrect

smat:RMI TCP Connection(74509)-10.8.121.130: ERR: 02/21/2017 11:49:36: Ignore this file and not attach it.

[Mike Keys]

Jim,

Thanks. Found out the receiving system ACK’s have an extra carriage return

1c 0d 0c instead of 1c 0d

[Mike Keys]

Jim,

Are you referring to the TPS section for the fileset protocol?

Also, don’t see a sample proc.

Yes, would be interested in your package/proc.

Thanks.

[Mike Keys]

Jim,

Thanks for your advice! I reused an older Tcl proc, rewrote some sections and created softlinks.

The Archive contains up to 60 days of uncompressed SMAT DB files for each process. The Tcl script runs right before midnight to try to get as close to capturing a full day’s worth. Even if the thread is cycled during the day, those SMAT DB files will be captured as well. The script also moved the LogHistory files and stats.

Mike

James Cobane wrote:

You can also move the SMAT DB files off, but simply soft-link the archive location under the $HCISITEDIR to allow the SMAT DB tool to access them.

[Mike Keys]

Perhaps it’s just getting used to the SMAT DB capabilities. Our current strategy is the current and previous day SMAT files uncompressed, then everything else is compressed and moved to an archive location. It’s a PITA to search and a PITA to uncompress and move back to its original location.

However, as much as this new DB will help, there are some that are very used to one file per process per day to look at and they want to keep that same “feel”. My question was how best to replicate this in the SMAT DB environment?

[Author]

Replies