set num [lindex $xlateInVals 0]
set strLength [string length $num]
set startLoc [expr $strLength – 8]
set date [string range $num $startLoc end-0]
set xlateOutVals

set num [lindex $xlateInVals 0]
set date [string range $num 8 end-0]
set xlateOutVals

IF the number is 3330520140417, the result I’m getting is 40417.  It’s basically trimming off the first 8 characters rather than trimming all but the last 8 characters.  I need to get the 20140417.

In that directory, you’ll see a client.ini file.  Delete it.  If you’re worried about deleting it, make a copy and put it…Read more

The problem was with the ACK/NAK and one not being sent back by the receiving system.  I finally tracked it down to the sending system not sending a value in MSH 15, which specifies how ACK/NAK are supposed to be handled.  

In the system we’re replacing, that system always sent “AL” in that field, to specify that…Read more

When this happens, in the recovery database, the message is in state 14 sending from the Receiving thread to the Receiving thread.  Here’s a screen shot

Created  Message Id     s e d Prio State Length Source          Dest

– – – —-

12:55:16 [0.0.213859943 P D N 8193    14   3063 to_logi_appt  …Read more

Here’s the end of the same interface in Test, that does not repeat:  ||||||R|Dx0d’

I’m going back to the sender to find out why I’m not getting that HEX to end the message in PROD when I got it in TEST.

The problem now is that I need to retain the file names, which are all unique.  In the set up now, on the outbound, I have to specify a file name, so all of my documents are losing the file names that I need, and are all under this generic…Read more

After that, I had no problems.

I’m on version 5.6 which is not supported on Windows 7.

It’s so annoying that when I need to look at the SMAT files by time, or verify when the last message has gone through on a thread, that I go back to my laptop.

Based on a couple of conversations with Jim, I’ve been using FRL and then the HRL to account for the repeating subfield, and then rounded it all out with a translation and have made some progress.  

So far, I’ve been able to get the document into 1 of 2 states:
1)  the entire report on one line — this happens when…Read more

I was getting bogged down with the details, and the number of fields that I needed to work with.  Once I saw your code, it ended up being fairly easy!

I’ve monitored this for a week now, and they are getting their messages just fine,…Read more

Normally, we used “SendOK_save” in the Send OK Procs field on the Outbound tab, and it works just fine.  But on the ones where we’re sending through a VPN tunnel and the…Read more

OK, I’m going to take this back to the person who started working on this, and make sure the output is what she’s looking for.  I’ve never done a flat file before but she needed a fresh set of eyes.

I’ve at least gotten data into the proper elements of the flat file, which I didn’t have…

The problem was with the proc I was using to append zeros to the number in PID18.  I compiled the translation several times, and bounced the process several times, with no luck.  Finally, I copied the proc, deleted it, saved the translation, compiled it, bounced the process, then put the proc back, saved, compiled,…Read more

The problem DOES seem to be in the TPS testing tool.  I do get a return in the production environment, and am able to successfully filter messages based on that value.

I even parsed the original message to be sure.

PID 3.3 equals

It doesn’t give me a return.  Since I’m sending to a test system, I think I’ll go ahead and put the proc on the thread and see what happens.  If it doesn’t filter, then there’s no harm done, and I can move on from there.

If it does filter, then I’ll…Read more

Thanks for your help!

Here’s a sample from the testing tool:
1(0).1(0).1(0).OBX(0).#3(0).[2].[0]  :  >LA01<
1(0).1(0).1(0).OBX(0).#4(0).[0].[0]  :  >1<
1(0).1(0).1(0).OBX(0).#5(0).[0].[0]  :  >Specimen/Source: SPUTUM/SPUTUM<
1(0).1(0).1(0).OBX(0).#14(0).[0].[0]…Read more