aborting jobs when data source empty

[will]

Hello,

Although the data source is empty either because the source server is down or simply because there is no data , the job runs perfectly.If i want the job to abort what could i do? Can i make use of the activity stages in the sequencer (eg terminator) or use the triggers to detect data source empty?

[ray.wurlod]

Yes, but prefer to issue a warning (UtilityWarningToLog routine) and exit (Terminator activity) rather than to abort.

Create a small job that selects COUNT(*) from source into a text file, then read this text file (Execute Command activity) then, depending on the result, either continue with regular processing or take the path described in the previous paragraph.

[kumar_s]

Iam still thinking a way to capture the file size (alone) from dos prompt.

[seanc217]

How about writing a Korn shell script to capture the size?
You could do an ls and pipe that into awk and capture the file size there.

[kumar_s]

How about writing a Korn shell script to capture the size?
You could do an ls and pipe that into awk and capture the file size there.

But its for windows.

[seanc217]

You can write shell scripts in windows utilizing the MKS toolkit. It is installed when you install datastage. The advantage to writing shell scripts is that they will translate to Unix with few problems. If you don't want to write a shell scripts, you could write a .bat file to check filesize before you run the job and only execute if greater than 0. Use a combiniation of the dir and find command in a command window.

Hope this helps.

[ray.wurlod]

Iam still thinking a way to capture the file size (alone) from dos prompt.

Code: Select all

test -z $filename

You have MKS Toolkit installed, so you have the test command. This can also be used in an if construct in a shell script using square brackets.

Code: Select all

if [ -z $filename ] ...

[kumar_s]

I guess test -z $filename is again a unix command.

[ray.wurlod]

Yes, but if you have DataStage 7.5x2, then you have UNIX on Windows (MKS Toolkit ships and installs with the product).

[sendmk]

Create a small job that selects COUNT(*) from source into a text file, then read this text file (Execute Command activity) then, depending on the result, either continue with regular processing or take the path described in the previous paragraph.

i wonder how you can make Execute Command activity fail/pass if source file is empty/full.

may be i did not get what ray told

pls somebody through some light.

[chulett]

i wonder how you can make Execute Command activity fail/pass if source file is empty/full.

By checking the result of the command. Perhaps it counts the number of records in the file, so you check to see if the returned value is 0 or >0. Perhaps it simply tests to see if the file exists and is empty or not empty, so you check to see of the returned value is true or false. Etc Etc.

Do the checking in the triggers you define in the Execute Command stage and branch accordingly. Custom triggers that check the StageName.$ReturnValue if I remember correctly.

[DSguru2B]

Iam still thinking a way to capture the file size (alone) from dos prompt.

May be you can try this. Did a search and found it.

Code: Select all

:: chk4zero.bat
@echo off
if %1'==' echo usage is: %0 FILENAME.EXT && goto :eof
if not exist %1 echo %1 was not found && goto :eof
if %~z1 EQU 0 goto :0
goto :eof
:: Put in any code you want to run if the file is not zero length.


::
:0
echo %1 is size zero
:: DONE

[sendmk]

did not find anything as given below,

StageName.$Returnvalue if I remember correctly.

my whole question is how to capture that return value in further actions.....

[ray.wurlod]

Exactly as Craig stated; ActivityName.$ReturnValue where ActivityName is the name of your Execute Command activity. If you're on 7.x you can select these "activity variables" from the "Add Parameter" button's dialog. In earlier releases (5.2 and later) they had to be entered manually, but could still be used.

Where and how did you look?