Clovertech

One thread for both in/out using the OVER command

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › One thread for both in/out using the OVER command

  • Creator
    Topic
  • November 14, 2006 at 8:09 pm #48888
    Ellen Shenk
    Participant

      Hello all,

      We are running Cloverleaf 5.3 on AIX.

      Has anyone tried to use one thread for both inbound and outbound by using the OVER $mh command in the tcl proc to put the transaction back on the inbound stack so it can route outbound?

      We want to route ADT to different processes using a thread like this to both receive and route the transactions to other threads.  I noticed that this thread always has a status of INEOF and never shows any record counts in or out.  I don’t like that.  Is that what others have seen as well or am I missing something?

      # set sourceconn to this threads name

      msgmetaset $mh SOURCECONN $HciConnName

      lappend dispList “OVER $mh”

      Thanks much for your help,

      Ellen Shenk

      Wellspan Health   717-851-2830

    • Creator
      Topic
    Viewing 0 reply threads
    • Author
      Replies
      • November 15, 2006 at 8:38 am #60009
        Robert Kersemakers
        Participant

          Hi Ellen,

          You need to add an extra line of code; this is the code we use:

          Code:

          set overmh [msgcreate -meta {USERECOVERDB true} [msgget $mh]]
          lappend dispList “OVER $overmh”
          lappend dispList “CONTINUE $mh”

          This way the message will also be sent as an outbound message, so it will be written and the outbound message count should go up. The inbound message count will remain zero though.

          Hope this helps.

          Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

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