Deborah Slater

Forum Replies Created

Viewing 3 replies – 1 through 3 (of 3 total)
  • Author
    Replies
  • in reply to: Accessing namespace procs #71353
    Deborah Slater
    Participant

      Hello Scott

      On the initial site that these namespace procs were written for:

          On the inbound TPS Inbound Data window, the proce tpsValidateBroadbandOrder is called and from within this proc there is a call to connid::write

      On the second site that uses the namespace proc, the same formula is used – it calls the tpsValidateBroadbandOrder on the inbound TPS Inbound Data window

      I just wanted to call the connid::write proc on a new site to save some data during the Xlate process, so I added the connid::write command to the tcl code : xltAAHGenConnID (attached) which is accessed on an xlate copy statement in the pre TCL Input/Ouput window. (You will see that I have noted out the call to connid::write and added in all the code as I needed to make the site avaiable for testing last week, but it would obviously be better to have the write proc just once and use it across our different sites.)

      in reply to: Accessing namespace procs #71350
      Deborah Slater
      Participant

        Scott,

        Thank you for agreeing to look further at my namespace proc access problem. Attached is the file containing the procs I am trying to access on the Xlate copy statement. I particularly want to use the connid::write, connid::read and connid::delete procs.

        Deborah

        in reply to: Accessing namespace procs #71348
        Deborah Slater
        Participant

          Thansk for the reply Charlie.

          I will have to investigate the whole package topic, as I don’t think this is something used here before. Which confuses me as I have examples of the procs I want to access being run in 2 different sites with the same qualified call structure and without any package require statements. Indeed there are no export statements in the tcl file containing the declaration of the namespace procs.

          The only differences I can find between the working sites and my site are:

             the working sites are being called from the inbound thread configuration tab in TPS Inbound Data, whereas on my site, I am trying to call the namespace proc from a copy statement in the translation.

            The other difference between the working sites and my one is that there are half a dozen procs in the .tcl file – three inside the namespace and three outside. On both the working sites there is a call to one of the procs outside the namespace first, whereas in my site all I am calling is a proc inside the namespace. Would this have any affect?

          In the meantime, I will look at the namespace export command and creating a package.

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