DSXchange

Hi,

I have an unix command its executinf fine in unix editor but when i tried to execute same command in datastage through execute command activity its throwing below warning

SH: -c: line 0: unexpected token 281 in conditional command
SH: -c: line 0: expected `)'
SH: -c: line 0: syntax error near `(28801>'
SH: -c: line 0: `if [[ $(ls -tr /etl/dev/target_files/work_files/spd_pyxis_adm/touch_files | wc -l) > 3 ]];then if [[ (T != "S") && (28801>=28800) && (28800<=72000)]];then echo "Source File Is Not Available " | mail -s "Hourly load job seq_Hourly_SPD_PYXIS_ADM:" XXX@yyy.com -r yyy@fff.com; fi;fi;'

provide some suggestions ..

Suggest you show us your script.

Hi,

Please look at this below unix command "
if [[ (28800<=72000) ]];then echo "Source File Is Not Available " | mail -s "Hourly load job seq_Hourly_SPD_PYXIS_ADM:" xxx@yyy.com -r dsadmd@yyy.com; fi;"

this command executing fine in unix environment , but when i tried to execute it through datastage in execute comand activity its saying below warnings .

SH: -c: line 0: unexpected token 281 in conditional command
SH: -c: line 0: expected `)'
SH: -c: line 0: syntax error near `(28800<'
SH: -c: line 0: `if [[ (28800<=72000) ]];then echo "Source File Is Not Available " | mail -s "Hourly load job seq_Hourly_SPD_PYXIS_ADM:" xxx@yyy.com -r dsadmd@yyy.com; fi;'

If you are going to use specific shell syntax (looks like Korn to me) then try specifying that in the Execute Command stage by prefixing it with the shell. So perhaps "ksh if..." might help. Use whatever shell you've coded for.

I thibnk:
SH: -c: line 0: syntax error near `(28801>'

is a clue. Looks like you need a space between the variable that is reprresented by 28801 and the >.

and Craig's suggestion is valid, DS executes basic sh commands and a lot of 'nix's don't . Most are either bash or ksh and you need to specify them to get things to work.

It it is working in the command line, find what shell you are executing and prefix the command there.

I agree you probably need to surround your operators with spaces. Also test it from the command line itself before pasting it into DataStage.

Your ticky marks look off to me.

I can't even make one it's suppose to be on my iPod touch.

Good point... The first mark is a tick and the last mark appears to be a single quote, which are different. I don't think you would want to use tick marks in this example.

I believe the backquote and upright quote are an artifact of the error report, and unlikely to be in the script itself.

Who writes stuff like that anyway?!!

Issue aside, is the following
going to give what you want? You are only ever going to get one "/etl/dev/target_files/work_files/spd_pyxis_adm/touch_files" file back from the ls so would imagine "wc -l" will only ever give 1.

Should it be "touch_files*" or a wc on the content of "touch_files"?

And may as well not list the file (or files?) by time order if the only purpose is to capture a line count.