There is nothing in your script that assigns a value to the variable DATA_SAS. The command:

Code:

export DATA_SAS=${DATA_SAS}

does absolutely nothing if DATA_SAS is a variable defined in your environment when your script starts (exported variables remain exported). If DATA_SAS is not an environment variable that is exported to your script, that command sets DATA_SAS to an empty string and exports it.

If we assume that the above command is a no-op and that $DATA_SAS expands to a string that is a pathname of a file, then at least one of the following commands in your script:

Code:

cd ${DATA_SAS}
YYYYMMDDb=`ls -1 f1_??????_????????.sas7bdat | tail -1 | extraire -c 11-18`
YYYYMMb=`ls -1 f1_??????_????????.sas7bdat | tail -1 | extraire -c 4-9`
cd ${TOOL_DIR}
export YYYYMMDDb=${YYYYMMDDb}
export YYYYMMb=${YYYYMMb}


} > $DATA_SAS 2>&1

has to fail. You can't change directory to a regular file; only to a directory. And you can't redirect output to a directory; only to a non-directory file.

If $DATA_SAS expands to an empty string, the redirection should fail with a syntax error.

If $DATA_SAS expands to a pathname of a directory, the redirection should fail.

If $DATA_SAS expands to a pathname of an existing regular file to which you have write permission or a non-existent file in a directory in which you have write permission, you should have gotten the output you wanted, but the attempt to change directory would have failed. Otherwise the redirection would have failed.

If we assume that $DATA_SAS does expand to the pathname of a directory, maybe you could get what you want if you change the line in your script:

Code:

} > $DATA_SAS 2>&1

to:

Code:

} > "$DATA_SAS"/logfile_name 2>&1