We are on 5.7.    Thanks for all the advice and alternatives.    I had a solution for my particular issue, but was just curious if it was do-able to iterate on the outbound variant.

Since I had a minimum of 2 OBX and a  max limit of 3 OBX’s (for a blood pressure vital),  I ended up simply doing an ITERATE on a list where the list was 0 1 2,…Read more

Jim Kosloskey wrote:
No you cannot iterate using an outbound element.

However, if you are on a release of Cloverleaf which supports Xlate Chaining then you can chain two Xlates, one that does the original ITERATE and then asecond one which now can ITERATE over the output of the first Xlate.

If you are not on such a release, then a method that…Read more

Jill Fredericks wrote:
We have experienced two Panics this week. During the second, the logging was on and indicated a problem with the variant, but we could not reproduce. We did however notice two messages with the exact same date/timestamp (MSH-7) passing through the xlate, 20120322162149. When we try to SMAT the file for a time range that…Read more

Jim Kosloskey wrote:
Jim,

I just tested this Cloverleaf 5.6 and it worked fine for me.

I set @contains to your value, did the IF (with else) referenced an inbound HL/7 field that is null and the False path was appropriately taken.

After a phone call to Jim (thanks Jim!) I came to understand that “ct” operator does not work like a “list…Read more

if I set a temp variable

COPY = M F O

BTW – we are on Cloverleaf version 5.7 Sun Solaris

Scott Folley wrote:
Are you using ACK/NAK processing on the receiving thread?

Thanks for the input.   It sounds like that certainly can’t hurt.    The hard part is that I can’t make it happen in test or production, so it will be hard to know if anything fixes it.   It just happens randomly on it’s own.    

I will update test and see how it goes.    Thanks again.

Jim

Jim Kosloskey wrote:
I should clarify it is XML with which I am not very impressed.

By the way what releas of Clovelreaf are you trying this on?

How large are these messages?

Me too.  Cloverleaf in general is wonderful.  

I figured it out, or rather a co-worker did.    When I compiled the XML the first time I didnt select a root.     I…Read more

Jim Kosloskey wrote:
Jim,

Hmmm… Just guessing here (as I said I have not done much with XML but not very impressed at this point) try enclosing your notation in curly braces like this:

set valPointer [grmfetch $gh {nm1:DOCUMENT_MESSAGE.nm1:document_data.&format}]

Thanks for the  reply.    That has been tried unsuccessfully.   Still…Read more

Jim Kosloskey wrote:
Klaus,

Here is what I would do:

I would build an Xlate (if you don’t already have one) and reference the field in question. The Xlate tool will give you the address path along with a reference to the repetition position (you already seem to have that but it never hurts to have confirmation).

Make sure you are getting what…Read more