Clovertech

Weird blank message

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Weird blank message

  • Creator
    Topic
  • January 24, 2013 at 12:14 pm #53486
    Tim Hallbauer
    Participant

      Hey All,

      Just wondering if anyone has seen this before.

      We are installing a new interface. Testing went fine. When the interface was migrated to PROD inbound mesages were causing errors. I could pull up the inbound result message in SMAT. It looked fine. I saved it off into a /tmp file and tried to look at it in an editing tool (UltraEdit) that I use fairly often. The only thing that shows in the tool, and at command line level, is the length encoding? No MSH, PID, etc…  If I hex edit it, it shows a number of blanks equal to the length encoding, but no data? All that shows is the length encoding?

      There is one inbound proc to blank out DNR result values. I ran one of the Test messages through the program and it worked fine. Ran one of the Prod messages through the same program and it comes out blank.

      Configs are exactly the same in Test and Prod. The vendor is insisting Cloverleaf is the culprit.

      Thanks,

      Tim

      I am stumped.

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • January 24, 2013 at 2:02 pm #77846
        James Cobane
        Participant

          If SMAT shows the inbound message fine, then there is something being done to the message once it is received.  I would suspect the proc, so I would take a hard look at that.  When you resend the message to a file from SMAT to edit, is there any ‘encoding’ being applied that may be causing the issue?  Is this a plain ASCII message, or is this some other encoding?

          Jim Cobane

          Henry Ford Health

        • January 24, 2013 at 4:33 pm #77847
          Tim Hallbauer
          Participant

            James,

            It’s just plain with no encoding. Like I said, I ran a Dev inbound saved transaction and a Prod inbound saved transaction through the same code. The Dev worked and the Prod didn’t.

            Tim

          • January 24, 2013 at 4:55 pm #77848
            James Cobane
            Participant

              I suspect the prod message is hitting some conditional logic within the proc that is producing the blank message.  Time to start adding a bunch of “echo” statements and running it through the wringer 🙂

              Jim Cobane

              Henry Ford Health

            • January 24, 2013 at 5:15 pm #77849
              Tim Hallbauer
              Participant

                We just had another call. Apparently the sending system had multiple interfaces pointing to us running at the same time. They got rid of the unnecessary ones and now it seems to be working????

                Thanks for the help.

                Tim

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