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 |
detail about sdlc
I have 100 records how can I load at a time from the single time
specify data stage strength?
what is diff b/w datastage 8.1,8.5,8.7?
I have 3 jobs A,B and C , which are dependent each other. I want to run A & C jobs daily and B job run only on sunday. how can we do it?
What is the use of surrogate key stage?
What is mapping?
how to use self join using datastage ? can u tell me using stage how can we implemnet the self join
What are system variables and sequencers in datastage
how to implement scd2 in datastage 7.5 with lookup stage
Suppose take my name "Reddyvaraprasad" From source it is coming Reddy vara prasad Need to get As Reddyvara prasad/
how many dimentions and fact tables used in your project and what are names of it?