Tip: hciroutetestshowbydest and hcitpstestshowbydisp

[Mike Strout]

Here is another usability tip until Infor implements some sort of favorite testing scripts widget.

It seems that better than 90% of the time, when I am using the testing tool, I am troubleshooting a route or a tps proc. I always used to roll my eyes it came time to find hciroutetestshowbydest or hcitpstestshowbydisp in the huge list of available procs in the Save Options section. Not anymore though.

I thought, these procs are just files, so why don’t I just add a duplicate of  the two I use all the time and add an _ to their name so they appear at the top of the list. It wasn’t quite that easy, but close.

As it turned out, these scripts are in routetest.tcl and tpstest.tcl respectively in the $HCIROOT/tclprocs directory. I created a new file named tmftests.tcl in that directory and then added the tcl procs from these two scripts into the new file. In each proc itself, I located the name of the proc and prepended the underscore and then saved the file. All that remained was a quick mktclindex and a restart of the client and _hcirouttestshowbydest and _hcitpstestshowbydisp are always at the top of the list.

Enjoy,

Mike

Topic

[Robert Kersemakers]

When testing tcl procs, you can find/select a proc by typing the first characters of the name; Cloverleaf will jump to the first occurrence.

Your method works great, but be careful. Making copies of a proc may lead to errors: you are testing/changing the copy, while in your NetConfig the other/original version is used.

BTW I have never used the route testing tool…

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Mike Strout]

Agree with all you said, though I find it more efficient if I don’t need to take my hands off the mouse.

As for the copying of the scripts, it will require a bit of manual maintenance, but we test things way more frequently than we update the Clvoerleaf-supplied scripts, so I think it is worth the effort.

Mike

[Author]

Replies