Want to suppress warnings for a job.

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
videsh77
Premium Member
Premium Member
Posts: 97
Joined: Thu Dec 02, 2004 10:43 am
Contact:

Want to suppress warnings for a job.

Post by videsh77 »

Hi

After job execution, we are getting following warnings -

APT_CombinedOperatorController,3: Field '<fieldname>' from input dataset '0' is NULL. Record dropped.


In my job I have following sequence -

Db2 EE Stage -> Transformer -> Seq File

As the number of logs exceed the view limit, there is no indication which stage is raising these warnings.

How can I be able to get rid of these warnings, with the identification of from which stage it has originated ?
Thanks with regards,
videsh.
gssr
Participant
Posts: 243
Joined: Fri Jan 09, 2009 12:51 am
Location: India

Re: Want to suppress warnings for a job.

Post by gssr »

videsh77 wrote:

How can I be able to get rid of these warnings, with the identification of from which stage it has originated ?
Set APT_DISABLE_COMBINATION to True

Set Warning limit to No limit while running the job.,else you can use message handler!
RAJ
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

My guess - it is coming from the transformer.

Handle nulls properly to avoid the warning. Never suppress them.
probal
Participant
Posts: 24
Joined: Sun Oct 25, 2009 10:17 am
Location: kolkata

Post by probal »

This is definitely because of the lack of the proper null handling in the transformer stage.go to the transformer stage , in the column metadata and double click on the column number,a new windows pops out where you can set the null field value.

ideally these should be done for all the columns having nullibility='yes'.

or you can use reject link from the transformer to catch the null values.
Probal
videsh77
Premium Member
Premium Member
Posts: 97
Joined: Thu Dec 02, 2004 10:43 am
Contact:

Post by videsh77 »

I have handled the nulls after retrieved from the database. While running a select, whichever columns were nullable, I have applies coalesce (db2 function) & replaced it with a space.
This suppressed the warning we received.

Thanks all for your valuable comments.
Thanks with regards,
videsh.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Are you aware of how you could have handled them in the job itself?
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply