Clovertech

Tclproc echos not seen

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Tclproc echos not seen

  • Creator
    Topic
  • April 30, 2012 at 7:40 pm #53069
    Johnny Anderson
    Participant

      CL v5.8, Sun Solaris 10, HL7 v2.3.1

      For site1 I have tclproc1 that shows echos when run under the testing tool, but when run under runtime thread (Route Messages,HCI_static route,Raw, Proc name), no echos. During debugging, I went to site2 and ran tclproc2. It shows echos for testing tool and runtime thread. I copied tclproc2 to site1 and run. Has echos for testing tool but not runtime thread. Tclproc1 and tclproc2 are identical and thread configs are identical. I searched the forum and found “Xlate Log Errors” Aug 2010 discussing EO config but no solution was given. I reviewed our EO configs and they’re all identical and I couldn’t find anything about echos. Here’s the tclproc:

      proc copy_hl7_file {args} {

             echo ”

      Tclproc copy_hl7_file begins

      “

             echo ” “

             echo ”

      Tclproc copy_hl7_file ends

      “

      } ;# proc-end

    • Creator
      Topic
    Viewing 8 reply threads
    • Author
      Replies
      • April 30, 2012 at 7:45 pm #76444
        Jim Kosloskey
        Participant

          Johnny,

          Since I have done this in the past I am not being snide when I ask about making sure you are looking in the correct process log for the echos 😳

          email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

        • April 30, 2012 at 8:26 pm #76445
          Johnny Anderson
          Participant

            I’ve attached the log showing process “process_log_process” and the thread config for “process_log_process” (2 slides).

          • April 30, 2012 at 8:32 pm #76446
            Jim Kosloskey
            Participant

              Johnny,

              When you added the Tcl proc to the route did you cycle the process to have the proc picked up?

              Also run with EO up and see if the engine is invoking your proc.

              email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

            • May 1, 2012 at 2:59 pm #76447
              Johnny Anderson
              Participant

                1. Q: When you added the Tcl proc to the route did you cycle the process to have the proc picked up?

                    A: No but did it today then a rerun, no echos, didn’t see a proc, log is attached.

                2. Q: Also run with EO up and see if the engine is invoking your proc.

                    A: See attachment, is enable_all correct? Then I did the rerun.

                I renamed the thread and process to better names.

              • May 2, 2012 at 1:40 pm #76448
                Bob Richardson
                Participant

                  Greetings,

                  From my understanding with some of our Operating Systems staff, the implementation of the “echo” command varies per platform.

                  Try using the TCL command “puts” and see if your statements appear in the process logs.

                  Just a thought.

                  Good luck.

                • May 3, 2012 at 1:30 pm #76449
                  Johnny Anderson
                  Participant

                    Jim- if I understand correctly, you said this tclproc must be associated with an xlate. I went to Thread Config and changed the process name to one that has an xlate.  Test has no echos. I have another site with the same config I’ve described here and the runtime test has echos.

                    Bob- the “puts” didn’t work, thanks anyway.

                  • May 3, 2012 at 1:43 pm #76450
                    Jim Kosloskey
                    Participant

                      Johnny,

                      No I said I did not see a message in the log you presented. Unless there is a message to route, the pre-route proc will not get invoked thus no echos (also no indication in the log the proc was invoked).

                      If you actually did have a message go through the routing then for some reason it did not show up in the log and that is quite unusual with EO enable all.

                      email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

                    • May 4, 2012 at 12:45 pm #76451
                      Bob Richardson
                      Participant

                        Gentlemen:

                        Just another thought here:  if the Tcl program is in the Pre or Post

                        Route upocs in the Xlate thread configuration and you want Start Mode logic to execute at startup, you need to check the “Run translation procs in start mode” box within NetConfig > Process > Configure.

                        Enjoy.

                        BobR

                      • May 8, 2012 at 7:19 pm #76452
                        Johnny Anderson
                        Participant

                          BobR, that fixed it, thanks.  I knew about this check box because I have setup similar tclprocs in other processes’ correctly.  In my original post on Apr 30, I stated “Tclproc1 and tclproc2 are identical and thread configs are identical”, I should have taken one more step and handled the “process” config. 😀

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