Same code works in TEST but not in Production.

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
rameshDHL
Premium Member
Premium Member
Posts: 21
Joined: Mon Nov 15, 2004 3:57 am

Same code works in TEST but not in Production.

Post by rameshDHL »

Hi,

I need to update the DB2 table in the flow, after inserting the values in the table. This logic is works fine in TEST environment,but when this deployed into production it doesnt. It dint say any error at all. Its in the sequence. If we run the job seperately it works fine.

Could any one have faced such a situation? Could you please help me in this to sort it out.

Regards
Sengan.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Not sure how anyone can help with that little information. :?

When something works on its own but not from a Sequence job, the first suspect would be the parameters being passed. Another thing to check is to Reset the aborted job (it does abort, yes?) and see if you get a 'From previous run...' message in the log.
-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 »

What's different between the two environments, particularly how the connection to DB2 is configured?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply