The 3rd line in your script:

Code:

fpath=. /sas/scripts/OPTUMize/output/disk_utilization/

sets the variable fpath to the string . and places it in the environment of the command it will then try to execute:

Code:

/sas/scripts/OPTUMize/output/disk_utilization/

which will fail with one of two errors producing a diagnostic message similar to:

Code:

./grpdsku.sh: /sas/scripts/OPTUMize/output/disk_utilization/: not found

or:

Code:

./grpdsku.sh: /sas/scripts/OPTUMize/output/disk_utilization/:  cannot execute [Is a directory]

Since you didn't show us anything like that in the output of the script that you ran, you didn't show us the script that you ran.

If, instead of:

Code:

fpath=. /sas/scripts/OPTUMize/output/disk_utilization/

your script had contained the command:

Code:

fpath=./sas/scripts/OPTUMize/output/disk_utilization/

(with no space between the period and the slash and assuming that your current working directory when you ran your script was not /), that would be likely to lead to the results you showed us. If instead of either of the above, your script had contained the command:

Code:

fpath=/sas/scripts/OPTUMize/output/disk_utilization/

(with neither the period nor the space), your script might do what you want. All of this is based on the assumption that the file you want to process is named /sas/scripts/OPTUMize/output/disk_utilization/disk_2016.10.25.txt and that there is no file named $PWD/sas/scripts/OPTUMize/output/disk_utilization/disk_2016.10.25.txt (where $PWD expands to your current working directory).