DSXchange

Hello
we have 2 jobs and
We have a requirement where in the job 1 we need to read the first record of a File and based on certain Key fileds i need to do a look up with Oracle table . if the key values exist in the oracle table then i need to abort the job and then as part of the job2 i can load the file to database.

So wondering is there a way to abort the job if look up is success.

I have other way where in as part of the job 1 i am mentioning the LookupFailure action=FAIL that means that there is no matching record and the job1 fails.In the sequence based on the status of job 1(abort) i can run the second job. I dont know how far it is valid.

any ideas

Thanks

You NEVER need to abort. Based on the lookup succeeding you need to make a decision about whether to initiate the second job. That is all.

thanks ray,

Wondering how to make the second job run because if the first job is succes (lookup success) means there is a matching record exists and if matching record exists i dont want to go to second job

Use a sequence. The first job records the result of the lookup somewhere (a file, its user status area), the sequence checks that and makes the decision about whether or not to run the second job.

In Lookup Stage use the Condition tab and put the equal condition and put condition is fail so that job1 will aborted then trigger the job2 based on triggers condition.

You will need need 3 jobs

1. Job1 which has lookup stage and captures the rejected data in Dataset1 and matched records in Dataset2
2. Job2
3. Job3 , In this job take Dataset2 and connected with a Basic_transformer and use this(If @INROWNUM >0 Then UtilityAbortToLog('aborted') Else 1) in the stageVariable (Note that your execution mode should be sequential)
4. this is how your Job sequence should look like

Job1
|
|
Job3---->Terminator Activity(In triggers, Expression Type should be Failed for this link)
|
|
Job2 (Expression type should be OK)

If there is any records in Dataset2 then JOB3 will Fail and goes to the Terminator Activity and If it runs OK then JOB2 will run successfully

thnaks thanush

As Ray suggested, it may be better to make your decision without having to abort. If you can use a file, store the results of the lookup into a sequential file in job1, use a command activity to see if any records were written to the file and invoke job2 based on the result using Nested condition activity.
HTH