why we use parameters instead of hard code in datastage
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
What are some different alternative commands associated with "dsjob"?
What are the main features of datastage?
Is it possible to implement parallelism in Mainframe Jobs ? If Yes how ? If no why ?
1.what is repartionoing technique? 2.what deliverables transferred to client using datastage? 3.how to write loop statements using nested loop sequence?
What is the difference between datastage and datastage tx?
How we can covert server job to a parallel job?
what is the use of skid in reporting?
How do u convert the columns to rows in datastage?
How will you move hashed file from one location to another location?
Define Merge?
What is a datastage job?
What are the types of containers and how to create them?
tell me 5 situations when we r using oracle db stages like orecle connector, oracle enterprise
How rejected rows are managed in datastage?
1)How will u implement SCD2 by using surrogate key. 2)What are the disadvantages with surrogate key. 3)How will you handle nulls in your project for the varchar, integer data types. 4)Can I use two fact tables in star schema. 5)3 jobs are running on the 2 nodes after I added one more node so can I compile those jobs to run on three nodes.