how to supress - no such file or directory unix error

Marley777 · Post by **Marley777** » Mon Dec 23, 2013 7:47 am

Hi, thanks for reading. I have a datastage job with a routine activity step. In the routine activity I use the following

"ls -1u /blah/blah/blah/FILENAME*.txt > /blah/blah/blah/FILENAME2.txt"

If FILENAME*.txt isn't found I get the 'no such file or directory error'. It is very common to not have a file in our situation. Can someone please show me how to modify the 'ls' command so that the error message is suppressed and the datastage job doesn't abort?

chulett · Post by **chulett** » Mon Dec 23, 2013 9:09 am

Typically one would redirect standard error to /dev/null.

Marley777 · Post by **Marley777** » Mon Dec 23, 2013 9:20 am

I have tried this

"ls -1u /blah/blah/blah/FILENAME*.txt > /blah/blah/blah/FILENAME2.txt > /dev/null"

and

"ls -1u /blah/blah/blah/FILENAME*.txt > /blah/blah/blah/FILENAME2.txt > 2 /dev/null"

but still get the error

/blah/blah/blah/FILENAME*.txt not found

do I need to change where/how I use "/dev/null' ?

chulett · Post by **chulett** » Mon Dec 23, 2013 11:13 am

Code: Select all

ls -1u /blah/blah/blah/FILENAME*.txt > /blah/blah/blah/FILENAME2.txt 2>/dev/null

Marley777 · Post by **Marley777** » Mon Dec 23, 2013 12:14 pm

Hi I gave it a shot, the DS sequencer still aborts. Looks like DS still knows somehow that the command could not find the file. Any other ideas are greatly appreciated.

rtneCreateList (ROUTINE DSU.ExecSH) started
13:05:33: rtneCreateList finished, reply=1
13:05:33: Exception raised: @rtneCreateList, Unhandled failure (1) encountered calling routine DSU.ExecSH

ray.wurlod · Post by **ray.wurlod** » Mon Dec 23, 2013 1:26 pm

DataStage detects the exit status. You can generate a fake exit status of 0 to prevent the warning. But... what do you then want DataStage to do in the case that the file does not exist?

Code: Select all

ls -1u /blah/blah/blah/FILENAME*.txt > /blah/blah/blah/FILENAME2.txt 2>/dev/null ; echo ""

chulett · Post by **chulett** » Mon Dec 23, 2013 1:56 pm

Sorry, should have been more specific - that suppresses the message but as noted you still have to handle the non-zero return status rather than leave it "unhandled". That's an option you turned on in the Sequence job and you can override that behaviour by handling the error yourself. Simplest way to make it see that you are handling any problems is with two triggers from the stage: an "OK" and an "Otherwise" trigger. If you don't care that it found no files then simply run both to a Sequencer set to Any before going on to the next step.