Jacques Talbot

Forum Replies Created

Viewing 10 replies – 1 through 10 (of 10 total)
  • Author
    Replies
  • in reply to: message delay questions #77512
    Jacques Talbot
    Participant

      Charlie Bursell wrote:

      Perhaps you are correct but the at command as I understand it will run the process at a given time.

      in reply to: message delay questions #77510
      Jacques Talbot
      Participant

        Charlie Bursell wrote:

        Aaron:

        in reply to: message delay questions #77509
        Jacques Talbot
        Participant

          Dustin Sayes wrote:

          using 6.0.2

          Does your script contain features that only work on 6.1?

          I know the hcicmd is normal command…

          I don’t understand this part of your script:

          $HciConnName prls_obd 1′ > /dev/null 2> /dev/null” | at now + $delay $unit > /dev/null 2> /dev/null

          Let me explain here is the complete line:

          Code:

          exec echo “hcicmd -p $HciProcess -s $HciSite -c ‘$HciConnName prls_obd 1’ > /dev/null 2> /dev/null” | at now + $delay $unit > /dev/null 2> /dev/null


          I ask tcl to execute the script in a shell

          The script start with an echo of a command that is piped for input to the at command.

          at will execute later :

          “hcicmd -p $HciProcess -s $HciSite -c ‘$HciConnName prls_obd 1’ > /dev/null 2> /dev/null”

          The at command usualy return the log and err with mail, so I redirected every output to /dev/null

          The hcicmd release one message with prls_obd .

          I think older 6.1 version prls_obd didn”t had a parameter, it was releasing everything that were on hold in the outbound.

          in reply to: message delay questions #77503
          Jacques Talbot
          Participant

            We are on AIX 6.1 and we have Cloverleaf 6.1

            May be you have an older version of Cloverleaf ?

            in reply to: message delay questions #77501
            Jacques Talbot
            Participant

              I found a clean way to delay messages. You must put the outbound tread on hold, and call the script in ob_tps that will release one messages latter with the unix “at” command. It take the parameters: DELAY UNIT and HCIPROCESS

              set gVersion:gTpsDelayMsg 1.0
              proc gTpsDelayMsg { args } {
              global HciConnName
              [code]
              set gVersion:gTpsDelayMsg 1.0
              proc gTpsDelayMsg { args } {
              global HciConnName

              in reply to: SOAP Envelope Schema #75738
              Jacques Talbot
              Participant

                http://schemas.xmlsoap.org/soap/envelope/

                Save it with a xsd extension. something like soap-enveloppe.xsd

                It will compile in the XML package manager.

                For the content I replaced the Body line:

                with the content type ref

                and I added the element declaration

                 

                 

                ….

                There maybe better way but it is working fine

                in reply to: Environment variable in a tps #67289
                Jacques Talbot
                Participant

                  Thanks all for your answers but it still not working.

                  I tried to set

                  set ::env(SYBASE) /path/to/sybase

                  didn’t work.

                  Tried in localInit.tcl no success…

                  I have no more time to try to make it work so I decided to write my script in a tcl shell and communicate with it with a socket.

                  Thanks again

                  in reply to: Environment variable in a tps #67286
                  Jacques Talbot
                  Participant

                    That file doesn’t exist

                    /hci/quovadx/qdx5.6/integrator/tcl/lib/localInit.tcl

                    Can I create it ?

                    In tps:

                    echo $env(SYBASE)

                    gave me:

                    ‘can’t read “env(SYBASE)”: no such variable’

                    from a tcl shell:

                    tcl>package require Sybtcl

                    3.0

                    tcl>sybconnect interface_ro inter10 snap01

                    sybtcl0

                    from tps:

                    puts [package require Sybtcl]

                    3.0

                    sybconnect interface_ro inter10 snap01

                    Error: sybconnect: sybconnect failed in dbopen

                    For today I can no more testing the BD is down, but I will comeback tomorow

                    Thanks

                    in reply to: Environment variable in a tps #67284
                    Jacques Talbot
                    Participant

                      I added

                      global env

                      but it doesn’t make my variable SYBASE visible

                      in reply to: I’ve spent too much time on this… #56120
                      Jacques Talbot
                      Participant

                        I had a similar problem and the only way I found was to use xpmstore:

                        xpmstore $xlateId [lindex $xlateOutList 0] c [format “%04d”  [lindex $xlateInVals 0]]

                      Viewing 10 replies – 1 through 10 (of 10 total)