Use a Wait For File activity in a job sequence. You can have one output from this when the file exists (or comes into existence within the required time period) that then executes your job. You have another output that is taken when the timeout expires without the file appearing. This does not execute your job at all.
By this means there's no need to abort anything; you retain complete control. Please refer to my recent Best Practices post for more.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I am not totally clear of your requirement. However, if you want abort a job you can use UtilityAbortToLog. You can find more information in the datastage documentation by searchin with the keyword Utility Transforms
sasikiran wrote:- If file is not found then I have abort the job and I have to send a mail saying that required file is not there.
Just run the job. If the file isn't there, the job will abort without you having to do anything. To send an email in that case, you'll need to use a Sequence job to run the job and trigger an email in the event of a failure.
If you want something more graceful, use a WaitForFile stage to check for the existence of the file first. Set the wait time to 0 to get an existence check. Then you can send a specific email when the file isn't found rather than assuming the abort is for that reason. File found, run the job.
-craig
"You can never have too many knives" -- Logan Nine Fingers
