Interested to Buy Any Domain ? << Click Here >> for more details...
why we use parameters instead of hard code in datastage
- 4 Answers
- 13177 Views
- HCL, I also Faced
- E-Mail Answers
Answer Posted / 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 |
Post New Answer View All Answers
Does datastage support slowly changing dimensions ?
What are the some differences between 7.x and 8.x version of datastage?
what is repositery?
What are the partitioning techniques available in link partitioner?
How can we improve the performance in datastage?
client know skid info?
Define ds designer?
Hi , Can anyone give few examples of scenarios and there corresponding design in datastage..i am new to this tool...confused in design while my manager asking to design the job.. Please post the URL if there..so i can go through it.. Thanks in advance...
What is a ds designer?
What are the types of containers?
What is the difference between passive stage and active stage?
DB2 connector> transformer > sequential file Data will be exported into a csv format in a sequential file. This file will be send in a email using a sequence job. Problem here is, how to avoid sending a blank csv file? When I ran the job there are chances that it might return zero records but in the sequence job csv file is going blank. how can I avoid this? thanks
Describe link sort?
What is the difference between an operational datastage and a data warehouse?
What all the types of jobs you developed?
