- This topic has 4 replies, 4 voices, and was last updated 6 years, 4 months ago by
.
-
Topic
-
A week or so ago I needed to split FT1 segments into their own DFT message and with help from here I got that to work great. But there’s a problem. Some of the charges are finally going through, but I still have an issue when the FT1 segment is repeated multiple times. Splitting the message still leaves the message control ID the same for all the new messages. I tried to increment that number for each iteration, but nothing changed so I’m sure I’m doing something wrong. I tried to follow some examples on here. I’d still like to try that but also want to ask if there’s a better way to make each message unique? CL 6.0.2 on Windows.
-
Replies
-
-
I don’t think that simply incrementing the number is the right approach. What if you have two inbound messages with control IDs are sequential. If you increment the first one it will conflict with the second. Maybe you can append extra characters or digits if you can do it in a way that will make it unique.
-
You could take the controlID and concatenate the FT1 segment setID to it. That way it makes it easily traced back to the source.
Concatenate MSH:10, -, and FT1(%g1).#1.[0] to MSH:10 within the iterate and before the continue.
Something like 1234567-1, 1234567-2, …
Or
Concatenate MSH:10, -, and $%g1 to MSH:10 within the iterate and before the continue.
This would uses your iterate counter with the first iterate being 0.
Something like 1234567-0, 1234567-1, …
Just thoughts. Hope it helps….
-
-
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
