HciConnName and Post Procs

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf HciConnName and Post Procs

  • Creator
    Topic
  • #49090

    Process: p1

    Thread: conn1

    Code:

    proc test { args } {
       keylget args MODE mode
       set dispList {}
       global HciSite HciConnName
       puts “HciConnName: $HciConnName”
    }

    When this proc is called as a Post Proc, HciConnName is set to “p1_xlate” instead of “conn1”. Is this a bug or by design? If by design, is it possible to get the name of the thread dynamically in a Post Proc?

    -- Max Drown (Infor)

Viewing 1 reply thread
  • Author
    Replies
    • #60703
      Charlie Bursell
      Participant

        This is by design Max.  HciConnName is supposed to contain the name of the owning thread.  Since the route pre and post procs run in the Xlate thread what you are seeing is the name of that thread which is always _xlate.  FWIW the command thread is named  _cmd.

        If you want the IB thread name at this point there are a couple of ways.  The more simple approach would be to get it from the metadata using the SOURCECONN key.  You could also store it in the USERDATA field of the metadata in an sms_ib_data proc

      • #60704

        Thanks, Charlie.

        -- Max Drown (Infor)

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