Save tclproc to root directory

Gary,

Once you put the proc in the $HCIROOT/tclprocs directory, simply change to that directory and run the ‘mktclindex’ command.  Once the tclindex is built, the proc will be accessible to all sites; they’ll show-up in the drop-down list in NetConfig.  One thing to be aware of is that when you upgrade to a new release, you’ll need to manually copy this proc to the new releases’ $HCIROOT/tclprocs directory; the normal ‘site promotion’ process will not move this proc to the new release.

Hope this helps.

Jim Cobane

Henry Ford Health

Gary,

Saving your procs to the HCIROOT can cause you issues on upgrade.

When upgrading Cloverleaf(R) the HCIROOT/tclprocs directory gets replaced and your procs go away. You would then need to replace them.

What can be done is to place the procs in another directory and sof link to them from the HCIROOT/tclprocs directory (assuming UNIX). You will ose the links on upgrade, but those are easily recovered.

If you are on 5.6 or later there is a Master Site feature that will eliminate the need for the links.

In either case (placing the procs in HCIROOT or linking from HCIROOT) to update the tclIndex just run mktclindex in the HCIROOT/tclprocs directory).

You need to be careful about running mktclindex in the $HCIROOT/tclprocs directory.  Doing so will break any Java UPoC’s you’re using, or won’t allow you to start using them in the future.  The procs that control Cloverleaf’s Java UPoC’s are stored in another directory ($HCIROOT/tcl/lib/tfc).  When you run mktclindex, it only looks in the current directory for files to include.  Therefore, the references to the procs in the $HCIROOT/tcl/lib/tfc directory will be lost.

Learned this one the hard way…  😳

TIM

Gary,

You can have the same proc in multiple sites.

But then you incur the responsibility of maintaining the same code in multiple sites – not a good idea.

If you are on Cloverleaf(R) 5.6 there is a Master Site specification which will allow you to share objects (procs are an object) among sites.

If you are prior to 5.6, you can build your own ‘Master’ site and if on UNIX use soft links (that is what we have done).

In our case, we did the mktclindex at the root level and experenced no hardship – perhaps because e do not deploy Java for anything ourselves and it does not appear to have harmed anything in Cloverleaf(R).

We will be utilizing the Master Site facility provided in 5.6.

Gary,

I hope my last response did NOT make it to this forum – fat fingered and it went as an incomplete message.

Ok… try again.

Given that the common tclprocs directory lives in:

 /quovadx/qdx5.6/integrator/allina_prod/tclprocs

and that the site which needs to find them is:

 /quovadx/qdx5.6/integrator/allina_prod2

 from this site do:  >ln -s /quovadx/qdx5.6/integrator/allina_prod/tclprocs

 and you should see (doing an ls -al):

 tclprocs -> /alin1hub_site1/qdx5.6/allina_prod/tclprocs

Note: the master site feature in CIS5.6 works fine EXCEPT (!) that you cannot modify any master site object other than in the master site within

the IDE !!!   For us this was unacceptable from a productivity standpoint and not what we had envisioned as how the master site needed to be implemented.

I hope this helps you out.

Gary,

If all of your sites have the symbolic link that points back to the master site (common site), the search sequence of the engine will be to look

in the local tclprocs directory first then at the root level.  There is a post somewhere on this Forum for the search sequence details.

Bottom line: the “local” tclprocs directory for a site is first; the link points to your master site (common site).  You cannot create both a local tclprocs “normal” directory and a link with the same name, that is, tclprocs.  This works for the other shared (common, master) engine files like Xlate, formats, Tables. etc.

We have used them for years without any problems.

Hope this helps you out.

Gary,

Yes, remove the local tclprocs directory first otherwise you will see an error that the directory already exists.

BobR