Clovertech

unexpected Mismatched IR Tags behavior

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › unexpected Mismatched IR Tags behavior

  • Creator
    Topic
  • December 5, 2011 at 9:54 pm #52833
    Anonymous

      I am getting a Mismatched IR Tags error in the Test gui when attempting to copy a literal (or anything else) to this AL1 segment.

      1(0).1(0).0(0).AL1.#1.[0]

      … and, the COPY statement fails.

      After verifying that the outbound address is correct many times, I tried moving the COPY statement up further in the translation.  When I move it above the PV1 COPY statements, I still get the Mismatched IR Tags error, but the AL1 COPY statement does work.  And, any subsequent COPY to the AL1 segment works fine, regardless of where it is in the translation.

      I have not tested this translation in a running process, and I know that the Test gui doesn

    • Creator
      Topic
    Viewing 1 reply thread
    • Author
      Replies
      • December 6, 2011 at 1:18 pm #75610
        Jim Kosloskey
        Participant

          David,

          Where the COPY is placed is not relevant.

          Since you say the COPY works even with the IR tage error present, I would suspect something else is causing that error.

          If you have not already, make sure your inbound variant matches your inbound message as to structure.

          Is there a BULKCOPY involved? If so, make sure your inbound and outbound variants match exactly.

          If not, one way to narrow this down (assuming Cloverleaf 5.6 or later) is to deactivate half of your Xlate Actions and see if the IR Tag error goes away. If it does then reactivate one half of the half you deactivated and test again. Continue that process until you find out what set of Actions is causing the error.

          If after deactivating one half of your Xlate the problem persists, reactivate that half and deactivate the half first left active – test again.

          Keep doing this ‘binary’ search until you narrow the culprit down sufficiently.

          Another option is to deactivate all but an innocuos Action (like COPY some literal to MSH-5) and see if the error persists.

          email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

        • December 6, 2011 at 1:55 pm #75611
          Anonymous

            Thanks Jim,

            We are running Cloverleaf 5.5P Rev1 on AIX 5.3.0.0.

            I know the placement of the COPY shouldn

        • Author
          Replies
        Viewing 1 reply thread
        • The forum ‘Cloverleaf’ is closed to new topics and replies.