Promote warning to fatal error

[vinaymanchinila]

Hi,

How do we promote a particular warning to fatal error so that the job aborts, we have a metadata mismatch , instead of generating a warning and dropping the data, we need it to abort.


Or

Is there a way to specify the job to abort after say 10 warnings when runing the job from Control-M.


Thanks,

[chulett]

Can't help with the 'promote the warning' bit, but I thought that was done via a right-click in the job's log on the warning itself?

Is there a way in PX to say if records go this particular link, abort the job after n of them? In the Server world you can say 'Abort after 1 row goes down this link' which stops the job at the first sign of the problem.

For Control-M and the 'dsjob' command line interface, simply add '-warn 10' to the command to start the job.

[vinaymanchinila]

Hi

We can demote or supress the warnings but not promote I believe.

The easy way is to use a transformer and use the condition abort on 1 row.

I have not tried the '-warn 10' , will try that, but was thinking if there is away to make a warning convert into FATAL.

Thanks for the inputs.

[ray.wurlod]

No.

[pneumalin]

Hi

We can demote or supress the warnings but not promote I believe.

The easy way is to use a transformer and use the condition abort on 1 row.

I have not tried the '-warn 10' , will try that, but was thinking if there is away to make a warning convert into FATAL.

Thanks for the inputs.

There is always a way to get what you want. But firstly you may want to identify how do you want to use this Job Abort/Fatal Status?

[ray.wurlod]

Not this time. You can detect and escalate, but you can not promote.

[kumar_s]

Isnt it not possible by message handler?
Or if it is metadata mismatch, collect it in reject link and add a transformer to "Abort after 1 row"

[ray.wurlod]

(1) No.
(2) This is "detect and escalate", not "promote".