why we use parameters instead of hard code in datastage
Answers were Sorted based on User's Feedback
Answer / ashok
not only security,for suppose i want to give another values
go to design and change the values it is not convinent for
user instead of this using parameters giving values at
runtime is flexible
| Is This Answer Correct ? | 5 Yes | 0 No |
Answer / shar
we use parameters for flexibility,re-usability in job design, values hard coding is a bad habit and bad practice.
lets say u have 20 fields and u have to pass them every time as and when data processing demands. Then every time going into the job and modifying the values is an unprofessional way and we sometime commit typographical errors.
instead of that use job parameters for reusability and we can use them any where flexibly depends on the parameters created at job level or project level.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / kiran
Hi Ashok..,
What ever Values u change run time(dynamically) which
purpose is called security.
Thanks
Kiran
8055902709
| Is This Answer Correct ? | 1 Yes | 4 No |
How many jobs in ur project? Explain any complex job u have done in ur project?
how can u handle null values in transformer stage.
Explain Quality stage?
Triggers,VIEW,Procedures
How to use Environment variable's in datastage?(use of process)
how many types of remove the duplicate records?
how many dimentions and fact tables used in your project and what are names of it?
With out using Funnel Stage, how to populate the data from different sources to single target
How can we do null handling in sequential files
Define Job control?
hi, 1)totally how many jobs created in ur project 2)what is ur datamart size & Dwh size 3)How secure ur project 4)could u plz tell be about testing process after complete the job will run sucessfully or not in Datastage
Name the third party tools that can be used in datastage?