Page 2 of 2

Posted: Tue Feb 06, 2007 2:47 am
by kumar_s
If you still want to abort the Job sequence, you can externalize the Abort functionality in a routine outside the job. Which check if the reject table is greater than 0 records for the current run, and calls the Abort signal accordingly.
As mentioned to you several times in the post and in the mail, you can use LinkRowcount to check the number of records that been passed to a link or if you maintain a table, you can count the number of records. Based that, you can use 'ABORT' or DsLogFatal().
Hope you are using BASIC routine for this purpose.

Posted: Tue Feb 06, 2007 3:48 am
by nvuradi
kumar_s wrote:If you still want to abort the Job sequence, you can externalize the Abort functionality in a routine outside the job. Which check if the reject table is greater than 0 records for the current run, and calls the Abort signal accordingly.
As mentioned to you several times in the post and in the mail, you can use LinkRowcount to check the number of records that been passed to a link or if you maintain a table, you can count the number of records. Based that, you can use 'ABORT' or DsLogFatal().
Hope you are using BASIC routine for this purpose.
hi thanks all for u r help i am able to abort the job using the function
DSLogFatal.

Thanks,
Naru

Posted: Tue Feb 06, 2007 7:56 am
by bkerebel
perhaps you could use too the
Call DSFatalInfo(xxx, yyy) to give a fatal message into your log

Bertrand

Posted: Tue Feb 06, 2007 8:07 am
by DSguru2B
bkerebel wrote: Call DSFatalInfo(xxx, yyy)
I have never heard of that function, you sure it exists :?