With QDX 5.6 it now seems to mostly dictate you do:
hcitcl $fileNameOfStandAloneTCLscript
This is a problem that I had to figure out a work around for because the technique of running TCL commands using “hcitcl -c $TCL_command” from within K-shell scripts is prevalant.
Personally I always thought it was a cool technique and would expect a bit more stability to the command line args to work into the future.
Here is an examples of one such K-shell command to illustrate what works in QDX 5.2 but breaks in QDX 5.6:
STATS=$(hcitcl -c “echo [oth_get_stats $thread]”)
Here is the replacement work around I decided to go with:
STATS=$(
hcitcl <<- !
echo [oth_get_stats $thread]
exit
!
)
Another approach would be to create a standalone TCL script that wraps around the TCL commands in a way they can be run from your K-shell.
My co-worker (Jim Kosloskey) and I decided against that for now when we added up the pros and cons.
Here is a usefull command I used to help me locate all instances of “hcitcl -c”
find . -exec grep -l ‘hcitcl -c’ {} ;
Russ Ross
RussRoss318@gmail.com