Why we use parameters instead of hard code in datastage.
Answers were Sorted based on User's Feedback
Answer / hanug
We use parameters to reuse the job multiple times by
passing different values to the job parameters.
| Is This Answer Correct ? | 8 Yes | 0 No |
Answer / nish
hard coding is a very bad practice.
You will face troubles once you deploy to production environment and need to make changes.
Instead if you parameteris and just make the change in original it will automatically update.
This is similar to your ATM card and pin. even if you change/update your pin the card will work.
If pin is hardcoded to the card and you need to change pin, then you need to get a new card everytime you want to change pin.
Does that make sense?
| Is This Answer Correct ? | 2 Yes | 0 No |
i have the source from Uk,north america how can i pass the data two tables based on the locations
can a fact table contains textual information
6 Answers HCL, HCL BSERV, IBM,
what is initial load and incremental load
If the job aborted in a sequencer, how can we start that from the previews successful job.
Can we use Round Robin for aggregator?is there any benefit underlying?
how to run a sequential file stage in parallel if the stage is used on the TARGET side
iam new to datastage...now i want to know what are fact tables, dimension tables in bank domain...if any body knows plz tell me asap..
how can we create a Sorrogate key in transformer stage? I want it in parallel mode
How to convert alpha Numeric values to alpha using functions?
plz tell me some dimentional and fact table names in banking project?
What is mapping?
How many input links can you give to a Transformer stage?