Parameter Substitution in OD script

I am using parameter substitution feature in my OD script.
I went through OD PDF in which they have mentioned the format as "$parameter^".
I tried using that format in my script and it worked fine.
In the same script i changed the format to "$parameter" and it gives me the same output as i got earlier.

Can any one tell me the reason behind the same? And which is the correct format that to be used?

Find more posts tagged with

Comments

Pawan

I am using parameter substitution feature in my OD script.
I went through OD PDF in which they have mentioned the format as "$parameter^".
I tried using that format in my script and it worked fine.
In the same script i changed the format to "$parameter" and it gives me the same output as i got earlier.

Can any one tell me the reason behind the same? And which is the correct format that to be used?

Did you check the logs for OD ? and specifying the od command or file would help in debugging your case.

Adam Stoller

I am using parameter substitution feature in my OD script.
I went through OD PDF in which they have mentioned the format as "$parameter^".
I tried using that format in my script and it worked fine.
In the same script i changed the format to "$parameter" and it gives me the same output as i got earlier.

Can any one tell me the reason behind the same? And which is the correct format that to be used?

The '$' and '^' are used to delimit the parameter within the config file so that it can be identified and substituted - however quotes (", ') also work for end-delimiter (possibly start-delimiter too, but I don't think so) - so:

foo="$bar^" and foo="$bar" will work identically

foo="$bar^_mumble" will work, but foo="$bar_mumble" will not (unless you also have a parameter named bar_mumble)

janhavi

Thanks a lot for the response.

Regards,
Janhavi