OK, we have understood that. Still, What RudiC has said holds:

Code:

gunzip -c "${i}" | $HOME/insert.sh > tmp/"${FILE}"

Here the script $HOME/insert.sh is called, but without any parameter, but here:

Code:

startTime="$(grep "<Setup" $1)</Setup>"
dn=$(grep -m1 "DN" $1)

It seems that one parameter to this script is required, no? So the line in script one should look like

Code:

gunzip -c "${i}" | $HOME/insert.sh "some-param-here" > tmp/"${FILE}"

and whatever yo put into "some-param-here" will end up where you use "$1" in the insert.sh-script.


Another thing is that obviously insert.sh expects the parameter to be a file(name), because otherwise this line:

Code:

sed  -e "/<Target/a\ $dn" -e "/<Target/a \ \ \ \ \ \ $startTime" $1 > $1.chg

wouldn't make any sense at all. But you do not pass a filename to insert.sh, instead you flood its stdin with input. insert.sh has no method to deal with input from stdin, though. It is as if you are writing someone a letter who is only expecting telephone calls. Because he watches the phone the whole day but doesn't check his mailbox you can write as many letters as you want, he won't react.

I hope this helps.

bakunin