Update existin rows only option's warnings

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
snassimr
Premium Member
Premium Member
Posts: 281
Joined: Tue May 17, 2005 5:27 am

Update existin rows only option's warnings

Post by snassimr »

Hi !

I need DS dont issue warning message if update sttaement dont find combination of keys for update statment. If it possible with ODBC stage ?
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Sure - stop sending update rows to it for keys that don't exist. :wink:

Seriously... hashed file lookup... existing keys... only issue an update when you get a hit on the hashed file.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

DataStage faithfully logs every warning it receives.

That way you can't sue IBM for not letting you know.

As Craig says, you can't suppress this; you must implement a design that does not generate the warnings in the first place. Such a job design will give you the additional benefit of running more efficiently.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Bala R
Participant
Posts: 66
Joined: Mon May 30, 2005 9:52 pm

Post by Bala R »

I have used the same tables as lookup using OCI stages, before I insert or update. Started the design with hashfile lookups and later changed to DB lookups. Have I gone down the wrong path?.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

As long as the performance is acceptable to you - no.
-craig

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