Clovertech

re: Healthquest TCP connection to engine

› Clovertech Forums › Read Only Archives › Cloverleaf › General › re: Healthquest TCP connection to engine

  • Creator
    Topic
  • July 8, 2005 at 6:59 pm #47887
    Mark Gathers
    Participant

      Hello,

      I’m looking for a contact that can help us resolve a TCP connection issue from our mainframe application, Medipac, to the engine.  Normally, our connection goes from OPENING to UP when messaging is sent from the mainframe to the engine.  However, sometimes the connection stays in an UP status and requires us to cycle the process before all returns to normal again.  I was wondering if anyone has experienced this problem.  Also, we like to know what TCP command should be sent to the engine when the application either closes its database files or the system is take down.  Any help would be appreciated.

      Regards,

      Mark Gathers  ðŸ˜†

    • Creator
      Topic
    Viewing 0 reply threads
    • Author
      Replies
      • July 9, 2005 at 1:28 am #56992
        Stephan Head
        Participant

          I am assuming you are talking about HUBO, right?  We have the same problem and it’s because HQ thinks it hasn’t received an ACK, even though Cloverleaf says it has sent one.  I saved the inbound and outbound logs to prove this.  When McKesson couldn’t fix the problem with program, SISBTTCP; we decided to do an Alert in Cloverleaf that has the HUBO thread “bounce” if the last read time is greater than 5 minutes.

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