Primary Site/Master Site – called TCL proc

I am encouraged that you got it to work. I tried putting the called proc ProcB in the Primary Site and the calling proc ProcA is in the current site. When the proc ProcA tries to invoke ProcB, it does not find it.

When you talk about a path for tcl procs, are you talking about physical directory?

I thought I tried every variation of recycling, after moving the called proc ProcB into the Primary Site. First I updated the Site Options of Site A to specify a site (SiteB) as it’s Primary Site. I recycled the host server and then I was able to see the SiteB objects in the SiteA NetConfig and other designers. Then I recycled the process in SiteA which contained the parent proc ProcA.

The invocation of ProcB from ProcA failed due to an unknown command. Maybe there is something else that has to be recycled?

This is the newer option where you can also define something like a Master site, called a Primary Site, differently for each normal / interface site. So we want to just have one site be the Primary Site for all the interface sites (I know this is just like Master Site. The reason we want to look at using Primary Sites is because we tried using a Master site before but there was a conflict when failing over with HACMP).

My understanding is that Primary Sites function exactly the same as Master Sites, but you don’t set that site at the root level, you set it for each normal site, in the site options.

🙂

I really want this to work. We have a few common “subroutine” procs called in multiple sites, just tripped over one this morning, and would really like to end up with one of each..

yes exactly.

I will try Max’s instructions – hopefully I missed something before.

I was unable to get that to work. I am on cis2022.09.01, on AIX 7.2

On the local site I restarted all processes and the two daemons, and I executed the Refresh Objects command. On the Primary site I ran mktclindex and also edited the TCL proc in the GUI to force the update of the .upocindex file. I ran Refresh Objects there also and I restarted both daemons. I’m still getting the error. I went back to the local site and ran mktclindex but that did not fix the problem.

tcl :out :INFO/0: to_email:11/09/2023 10:33:00] sourceFilter /hci/cis2022.09/integrator/soabattst/tclprocs/email_smtp_mime.tcl: Failed to source filtered file: couldn’t read file “/hci/cis2022.09/integrator/soabattst/tclprocs/email_smtp_mime.tcl”: no such file or directory
[sms :sms :ERR /0: to_email:11/09/2023 10:33:00] Tcl error:
[sms :sms :ERR /0: to_email:–/–/—- –:–:–] msgId = message0
[sms :sms :ERR /0: to_email:–/–/—- –:–:–] proc = ‘extracts_email_send’
[sms :sms :ERR /0: to_email:–/–/—- –:–:–] args = ”
[sms :sms :ERR /0: to_email:–/–/—- –:–:–] result = ”
[sms :sms :ERR /0: to_email:–/–/—- –:–:–] errorInfo: ‘
[sms :sms :ERR /0: to_email:–/–/—- –:–:–] invalid command name “email_smtp_mime”

Just to be clear, the above folder name: /hci/cis2022.09/integrator/soabattst is a link, and all the local sites are in a different file system, with links to them stored in the integrator folder. Our master site is in a sub-folder in the integrator folder (/hci/cis2022.09/integrator/clovertest/<site content>); our local sites are in a different file system (/test/cis2022.09/soabattst/<site content>). Does that make a difference?

Now that I have gone through all that and documented the error messages, it just started to work. The only thing I changed was to update the calling proc, in the local site. I don’t know why this made a difference. I looked in the .upocindex file and the tclindex file, in both the local site and Primary Site, and while these were updated at the same time, I don’t actually see the called proc, in the Primary Site, listed in the local site’s upocindex/tclindex files. But the update to the calling proc and the subsequent recycle of that one process which invokes the parent proc seems to have closed the loop. I did not see this activity documented anywhere as required. But nothing else changed.