Xlate INCLUDE Action sub Xlate be a different HL/7 version?

[Jim Kosloskey]

I am experimenting with the INCLUDE Action.

My experiment is to try to have a sub Xlate that handles the IN1 Group in an OB HL/7 2.9 message but the source is HL/7 2.4.

So, 2.4 to 2.9 ADT messages.

The IN1 2.4 group is at a different Address Path Prefix {5(0).0(0)} than the IN1 2.9 Group OB {9(0).0(0)}.

In the Sub Xlate (to handle the IN1 Group) there is an ITERATE in play.

In the Host Xlate I specify the IB Host Prefix and Sub Xlate Prefix to 5(0).0(0); the OB Host Prefix to 5(0).0(0) and the Sub Xlate Prefix to 9(0).0(0).

The Host Xlate uses the default 2.4 HL/7 Variant IB and OB and the Sub Xlate uses the default 2.4 HL/7 Variant IB and the default 2.9 HL/7 Variant OB.

Via the debugger, I see the Xlate stepping through the Actions of the Sub Xlate but nothing appears in the OB message or the expression I am watching for one of the IN1 OB Components.

When I do the same for the PID segment where the Prefixes match for 2.4 and 2.9 all works as expected.

Can INCLUDE reference a sub Xlate which uses a different format OB than the Host OB structure and have a message built or is the parser not able to resolve the address path differences (but not complain about it)?

Anybody had any experience with this?

Cloverleaf 2022.09 on Windows.

Thanks

 

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

Topic