[Jason]

Hi Jim,

just seeing this now, can I get a copy of that script?

thanks in advance

[Jason]

found it:

 

https://education.infor.com/

[Jason]

sorry, should’ve clarified, it’s not in the actual IF statement, it’s setup like you described

basically, it’s saying @result eq=N when I’m expecting it to be Y

[Jason]

Charlie,

That worked! thanks! learned something new too

[Jason]

perfect, thank you, I will give it a shot!

[Jason]

Charlie,

oh I see, no I don’t want it to start again, I want it just forget the file.. like stop processing that file period. I’m assuming in order to do this, I’d need to delete that fileset<thread> file and the source file it is reading from??

edit, I suppose another question would be, should I just delete the source file? I have limited visibility into the file structure of where this Cloverleaf server sits so I assume the source file is just sitting there? and then, normally, gets deleted when when the file is finished processing?

• This reply was modified 2 years, 6 months ago by Jason.

[Jason]

I see the fileset-<Your Thread name> file in the process directory.

It’s safe to delete this file??

 

[Jason]

yeah I don’t want to affect other threads in the route… so all the queued messages should be in the recovery DB?

The way that process is, there’s two IBs feeding one OB. I just want to flush out this one IB without affecting the other one

edit: I can’t find the messages in the recovery DB… my recovery DB is empty

• This reply was modified 2 years, 6 months ago by Jason.

[Jason]

hmm good question, is there an easy way to compare them?

[Jason]

Charlie,

yes, you were right, it was a 0x0D, my bad.

Thank you for that. So what I did was basically what you’re suggesting but in C# instead of Perl.

Appreciate you taking the time reply.

Cheers!

[Jason]

Or would it be better/easier to output the SQL HL7 to XML and use that in the Cloverleaf input?

[Jason]

Thanks @Paul, that is good to know!

[Jason]

@John – yep, just realized this, my confusion was that the inbound HL7 variant had the same 48 character limit defined but for some reason it came through with more than that… but either way, once I increased the length on my outbound variant field, it came through fine.

[Jason]

ok, I think I fixed it, I had to update the field to unlimited and then it came through.

Couple questions,

1) why didn’t the inbound HL7 message follow the 48 length restriction and get off as well?

2) what does it mean when a segment, in the HL7 configurator, is blue italicized ? I’m assuming it means it’s been modified but when I modified the PID#5 to be unlimited length the HL7 variant segment didn’t turn blue…?

Thanks!

[Jason]

Charlie,

Just looked through the script, great work, but where are you actually writing into the Tables? maybe I missed it, I guess that’s the crux of the issue.

Thanks

[Author]

Replies