job debugging

kripakrish · Post by **kripakrish** » Fri Apr 13, 2007 1:07 pm

Hi all
I am a data stage newbie .I have been going through the forum(It is very very helpful) and running sample jobs. I came across the @false constraint technique to identify bottlenecks.Are there any other methods of conditional link execution.
Note: If I am not clear like in C we have #Ifdef and #ifndef similarly if I have to execute selected links what are the possible methods?

DSguru2B · Post by **DSguru2B** » Fri Apr 13, 2007 1:24 pm

I am confused. The phenomenon your are mentioning in C is during coding. You cannot code like that within constraints and stage variables. In a basic routine you have $DEFINE, $IFDEF, $ENDIF etc. which are listed in the BASIC.pdf that gets shipped with the product. You can go through it. If you expect a different answer, please clarify your question.

kripakrish · Post by **kripakrish** » Fri Apr 13, 2007 1:30 pm

Sorry If I was not clear. I am trying to debug if the problem is with data base or data stage right, then in the transformer I use @flase constraint only to extract data and not further down the job. My question is how can i selectively disable few links (in passive stages) to identify bottle necks.
Hope I am clear. Any other debugging methods appreciated.

Thanks

DSguru2B · Post by **DSguru2B** » Fri Apr 13, 2007 1:37 pm

You can build a portion, test it, build another portion, test it. What exactly is the bottleneck. Share your design and system info with us. What you are trying to do etc.
You cannot selectively disable links and stages, other than sending nothing down a stream, using @FALSE constraint.

kripakrish · Post by **kripakrish** » Fri Apr 13, 2007 1:41 pm

Thanks for response.
Today I was able to identify the problem with my job using @false technique in transformer.I found it useful.So I want to know more such techniques of debugging server jobs. (like debugging job best practices).It will be helpful as i am a beginner with data stage.

Also I was expecting your customary welcome as this is my first post!

chulett · Post by **chulett** » Fri Apr 13, 2007 1:44 pm

DSguru2B wrote:You cannot selectively disable links and stages, other than sending nothing down a stream, using @FALSE constraint.

Sure you can! Think job parameters. One per link or situation, setting it to true or false, yes or no - whatever makes sense to you.

Then add it to your constraint - blab blah blah AND LINK2_ON = 'Y'.

All kinds of ways.

DSguru2B · Post by **DSguru2B** » Fri Apr 13, 2007 1:49 pm

Execution cannot be disabled, it can be constrained using a bunch of ways, including ones you mentioned. But it will be executed. Its not synonymous to C's #Ifdef and #ifndef.

kripakrish · Post by **kripakrish** » Fri Apr 13, 2007 1:55 pm

Thanks Craig I would have never thought of it.Thanks dsguru for reply

Constrained vs executed...ah now I am getting the difference.I . Can you please share how to constraint data flow in a job? If we can add to the list it will be useful for other newbies
1. @false in transformer
2. Job parameters and enable/disable them in various branch paths