Clovertech

FRL to X12 route trix id error

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › FRL to X12 route trix id error

  • Creator
    Topic
  • April 17, 2017 at 12:20 am #55367
    Ellen Roy
    Participant

      Hello,

      I am using the testing tool to test the route in my network config for an FRL to X12 translation.  I am getting an error.  I have selected a trx id determination format of X12 on my outbound thread and when I try to run a file through I get the following error.  Any ideas for what I should change?

      This is an X12 278 outbound for UHC.

      Output going to stdout

      [xlt :rout:ERR /0:  UNNAMED_TID:04/16/2017 19:19:07] No routes defined for TrxId ”

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • April 17, 2017 at 2:41 am #85081
        Jim Kosloskey
        Participant

          If this is FRL to X12, then your TrxID would be on your inbound thread and be FRL not X12.

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

        • April 17, 2017 at 1:30 pm #85082
          Ellen Roy
          Participant

            Jim, I have my in_thread and my out_thread.  On the in_thread I set the

            trx ID format to FRL on the inbound tab.  On my out_thread I set the Trx format in the inbound to to X12.  That produced the error I posted.  After reading your reply I changed the Trx ID format on the out_thread also to FRL and this produced the same error on test

            Output going to stdout

            [xlt :rout:ERR /0:  UNNAMED_TID:04/17/2017 08:26:25] No routes defined for TrxId ”

            I am not able to remove the Trx ID from the out_thread to have it be blank and try that.

            When I compare my network config to other interfaces built onsite, I thought I understood that the Trx id format on the out_thread needed to be defined as the format after going through translation.  Can you clarify what my goal should be on this?

          • April 17, 2017 at 2:23 pm #85083
            James Cobane
            Participant

              Ellen,

              If you are not expecting any ‘inbound data’ on your outbound thread, there is no need to configure Trx ID on the thread.  If you are expecting any type of reply on your out_thread, then you need to handle it as such (either via procs or reply routing).  The configuration of Trx ID on your outbound thread has no relationship to the configuration specified on your inbound thread.

              Hope that makes sense.

              Jim Cobane

              Henry Ford Health

            • April 17, 2017 at 9:04 pm #85084
              Jim Kosloskey
              Participant

                Is this File based or real time? What is the protocol for your outbound thread (to X12)?

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

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