How to abort a job?

kumar_s · Post by **kumar_s** » Mon Sep 05, 2005 1:34 am

Hi DSXians,
May i know the way to abort a job based on a calculaiton (probably from a transformer). Like a UtilityToAbortLog() available in server.
Is there any built in routines or functions available.

I need to calculate number of reject records and at once if it exceed 2% of source, it should be aboted

regards
kumar

dsusr · Post by **dsusr** » Mon Sep 05, 2005 2:00 am

Hi Kumar,

You can use the same utility by using the Basic Transformer in your parallel canvas but you need to pass the number of records in source as a parameter to the job.

Then you can implement the logic by using stage variables in the transformer.

Regards
dsusr

kumar_s · Post by **kumar_s** » Mon Sep 05, 2005 2:43 am

Hi dsusr,
I understand that, but the whole point of aborting the job before it get finished is to make the job more effecient (to lower the run time). But as we know, Basic transformer is not the suitable stage in PX as for as effeiceny is concern

.

regards
kumar

kumar_s · Post by **kumar_s** » Mon Sep 05, 2005 4:48 am

This is not only to abort the job, it would be better if it is possible to stop the whole flow once it reaches the condition....

regards
kumar

Amit Jaiswal · Post by **Amit Jaiswal** » Mon Sep 05, 2005 6:25 am

Hi Kumanr,
You can call shell command wc -l to count number of rows in source if it is a sequential file (equivalent for other) using Before-Stage. This number you can use to determine %age of failure. Then inside a Transformer Stage take one stage variable in which you can write your logic and return a flag based on your requirement. Take this flag as a constraint for any link and specify Abort after rows as 1 or as per your requirement in the Constraint dialogue box.
Hope this will work for you.
-Amit

kumar_s · Post by **kumar_s** » Mon Sep 05, 2005 12:07 pm

Two transformers, one for calculation.... one to abort.....
Hummm..... worth trying

Thanks amith.

regards
kumar

ray.wurlod · Post by **ray.wurlod** » Mon Sep 05, 2005 4:13 pm

Best practice is never to abort, to remain always in control.

chulett · Post by **chulett** » Mon Sep 05, 2005 7:29 pm

Sorry, not exactly a constructive comment, but I found something amusing in the concept that you make the job more efficient and shorten the runtime by aborting it.

I guess that's as opposed to letting it continue to run when you know things are going south and will need to be rerun.

kumar_s · Post by **kumar_s** » Mon Sep 05, 2005 9:58 pm

Hi,
I too agree with your words that not to be aborted.
But the input file is Veryyy... huge. If it reject more that 2% for a condition, the input file should be reprocessed.
The actual requirement is to stop the flow of the job.
Since i dont know how to stop the flow i am aborting it with some log

.

regards
kumar

kumar_s · Post by **kumar_s** » Mon Sep 05, 2005 10:00 pm

Hi,
I too agree with your words that jobs not to be aborted.
But the input file is Veryyy... huge. If it rejects more that 2% for a condition, the input file should be reprocessed. And if it starts to reject it would reject in early number of records.
The actual requirement is to stop the flow of the job.
Since i dont know how to stop the flow i am aborting it with some log

.

regards
kumar

roy · Post by **roy** » Wed Sep 07, 2005 2:13 am

Hi,
What about stopping the job? ( DSStopJob() )
DS 7.5 introduced the Terminator Activity for sequence jobs that has an option to send such stop requests to running jobs.
This sohould be a safe alternative to aborting jobs.

IHTH,

battaliou · Post by **battaliou** » Wed Sep 07, 2005 5:34 am

You could always divide by 0 if you want a quick failure.

DSXchange

How to abort a job?

How to abort a job?

Re: How to abort a job?

Use Abort After rows

Re: How to abort a job?