Mycom relies on having the unit-ID for loading the data.
Unit-ID = Link + A/B = link endpoint
The LTP external label offers a place where the Unit-ID could be written to, but it was agreed in the past only to write the LinkID into it.
Theoretically the A/B side can be determined from mountname+linkID.
It needs to be decided upon how to obtain the Unit-ID.
If we don't have the information inside the CC and if we are determining it by some ruleset we need to ensure that this matches the CM data (e.g. provided by APT) and we don't mixup A and B side.
(Also for the start we will still get PM data from CAINN and if there A/B are different than in Mycom data this leads to insufficient data.)
My proposal would be to write the Unit-ID into the ltp external label, as the Link-ID can simply be derived by removing the trailing A or B from the Unit-ID.
Mycom relies on having the unit-ID for loading the data. Unit-ID = Link + A/B = link endpoint
The LTP external label offers a place where the Unit-ID could be written to, but it was agreed in the past only to write the LinkID into it. Theoretically the A/B side can be determined from mountname+linkID.
It needs to be decided upon how to obtain the Unit-ID. If we don't have the information inside the CC and if we are determining it by some ruleset we need to ensure that this matches the CM data (e.g. provided by APT) and we don't mixup A and B side. (Also for the start we will still get PM data from CAINN and if there A/B are different than in Mycom data this leads to insufficient data.)