Thread Parsing Errors, need a new set of EYES

[mike brown]

Please tell me why am i getting the following, I kinda need help with NetConfig Dump

and getting the following…

syntax error at line 6 : `(‘ unexpected any and all help welcomed.

In the following PROCS…

getroutedata :

######################################################

# Tcl program to obtain Routing info for each thread

# Author: Mike Brown

Topic

[David Barr]

Because you’re running the script with a Bourne shell interpreter instead of a TCL interpreter.

[mike brown]

thanks for replying

Oh Ok, help me out a minute should i rewrite the code or change the extension, i am at a loss right now

mike

[David Barr]

You’ve got this code in a file, probably called something like foo.tcl. Instead of typing “foo.tcl” or “./foo.tcl” to run it, type “tcl foo.tcl”.

There are other more complicated ways of dealing with this. You can add a “shebang” line to the top of the script (#!/quovadx/qdx5.7/integrator/bin/tcl), but then you’ve got to worry about maintaining the script every time that Cloverleaf is upgraded.

You can add lines like this to the top of the script:

Code:

#!/bin/sh
# the next line restarts using tclsh
exec tclsh “$0” “$@”

Personally, I like to keep it simple and say “tcl foo.tcl” wherever  I’m calling my scripts.

[mike brown]

Thanks David big time that really works.. i am now able to complete my task.. thanks again..

mike

[Jim Kosloskey]

Dave and Mike,

Actually if you put the following at the front of your Tcl proc you will be unaffected by Cloverleaf upgrades:

#!/usr/bin/ksh

# this line to escape the next line from the tcl interpreter

exec hcitcl “$0” “$@”

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

[Charlie Bursell]

Even better Jim, try this:

#!/usr/bin/env tcl

or for perl

#!/usr/bin/env perl

[Jim Rawls]

Charlie,

If we use your Tcl invocation method, are the hci Tcl extensions still available to the proc?

[Jim Kosloskey]

Charlie,

Even better – I will start using that.

Thanks

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

[Charlie Bursell]

Assuming the root is set, yes

Try it and echo out the variables you want.

[Bob Richardson]

Jim and Charlie,

I have experimented with the KSH method and found that I have problems in passing shell arguments ($1… $N) into the script

for the hcitcl program to interpret.

Do you have a suggestion for how that can be accomplished?

Admittedly not “korny” enough on my part.

Thanks.

[Charlie Bursell]

Don’t really understand the problem Bob.

You pass args on the command line like any other script:

     mytcl  arg1 arg2 arg3 etc

in your script you should have a line at the end of the script like

    procname $argv $argc

argv will contain a list of command line args while argc will contain the number of args

The proc you are calling should look something like:

proc procname {argv argc} {

Just habdle argv and argc in the proc

[Bob Richardson]

Charlie,

Thanks.  I will redo my experiment and report back to this forum on results.  I do have the code statements you illustrate in my hcitcl program.

Most likely will have to wait until next week as this week I am the turkey in the hot seat for problems (the on call bain of IT).

BobR

[Jim Kosloskey]

Bob,

Virtually all of my command line Tcl scripts use command line arguments and I don’t have any issues.

If you would like an example of a command line proc I have utilizing arguments, email me and I will send it to you.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

[Author]

Replies