Search Results

I think that code in unquoted here documents is problematic: too many levels of quoting.
In zsh you can chain two (or more) redirections
#!/bin/zsh
filepath=/xxx/yyy/zzz/
filename=xyz

ssh...

Since there is only one input file and one output file in your original code:
read header < $infile
lineout=...$header...
echo $lineout >> $outfile

while read dataline
do
...

Every time you do <$infile, it's re-opening the file, just because that's what it means.

If you want to open the file only once, you can do this:

exec 5<$infile # Open into file descriptor 5
...

awk -F, '{a[$1]=($1 in a)?a[$1] OFS $2:$2} END{ for(i in a) print i,a[i]}' OFS=, myInputFile.txt

Yes, there is nothing special about the export command it is just another builtin command that also happens update the value of a variable. The real issue is that variable assignments are treated...

For ksh try export

#!/bin/ksh
function getParams {
for param in $@
do
export $param="$(db2 +w -x "SELECT PARM_VALUE_TXT FROM ${FRMWRK_DB_SCHEMA}.JOB_PARM WHERE PARM_NM='$param' WITH UR")"...

To enter a control character, type Ctrl-V followed by the control character you need (Ctrl-Y in this case):

$ grep '^YCAT^Y' testfile
CAT
$You can't see the control characters in the output, but...

Your problem arises from the fact that "find" is not a shell and does not know how to process the pipeline character '|'. My solution would be to switch to a shell. My login shell is ksh so I can...