Can’t send message to Error DB in UpoC 5.3?

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Can’t send message to Error DB in UpoC 5.3?

  • Creator
    Topic
  • #48373
    B Pariyesana
    Participant

      Happy Friday,

      Can we send message to Error DB in UPoC Protocol in CLoverleaf 5.3? I wrote a UPoC TPS that will send message to Error DB if a script is not exist, but looks like instead of sending that message to Error Db, it requeued the message.

      Here is what I put in my TPS

         if {![file exists $script]} {

            WriteError $module “the kermit sript $script is not available, send msgs to Error DB”

            return “{ERROR $mh}”

      and here is what show up in the log file

      [ERROR: (tpsKermit/trailblazers_out) Fri Mar 03 17:11:03 EST 2006] the kermit sript trail_send.ksc is not available, send msgs to Error DB

      [pd  :pdtd:INFO/1:trailblazers_out] [0.0.44088] Writing message failed

      [pd  :thrd:INFO/0:trailblazers_out] [0.0.44088] Requeuing undelivered message

      [msg :Msg :INFO/0:trailblazers_out] [0.0.44088] Updating the recovery database

      [dbi :rlog:INFO/1:trailblazers_out] [0.0.44088] Update msg in recovery db to state OB post-SMS

      Does anybody know whether it’s possible to send message to Error DB in UPoC protocol or not? I know that we can do that in Outbound TPS because I did that before. Is it something new in 5.3?

      Thanks

      Budhi Pariyesana

      Sr. Interface Engineer

      MedStar Health

    Viewing 2 reply threads
    • Author
      Replies
      • #58438
        Scott Folley
        Participant

          I don’t know about this specifically, but I do know that we used to disposition messages in a UPoC protocol driver as a KILL prior to 3.8 and had no difficulty with that.  As of 3.8 and above this is something that you have to do in the Outbound-TPS.  I strongly suspect that whatever change was made to the UPoC protocol driver to eliminate that functionality also impacted the ERROR disposition.

        • #58439
          B Pariyesana
          Participant

            Thanks Scott.

            For quovadx people:

            So is it a bug in Cloverleaf 5.*?

            Thanks

            B. Pariyesana

            Sr. Interface Engineer

            MedStar Health IS

          • #58440
            Charlie Bursell
            Participant

              It is not a bug but more a method of implementation.  Remember that the UPoC driver is just that, a driver.  Once Cloverleaf has delivered a message to the protocol driver it has completed it’s task.

              If you wrote a TCP/IP driver or any other driver in language, it would be your job to handle errors at that point.  With that said, there are methods, with a little ingenuity, to send UPoC driver errors to the error database.

              FWIW, we have an enhanceent request to change the way it works but it is not as easily done as said.

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