Is it possible to pass a job parameter inside another?

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

yabhinav
Participant
Posts: 37
Joined: Wed Mar 05, 2008 11:54 pm
Location: Hyderabad

Post by yabhinav »

@Craig
All the columns are concatenated using a single column (each delimited by a comma) and the output of the query is sent to a file. So instead of building separate ETLs for each output file, I can do this in a single ETL and also give the end users the flexibility to select as many number of columns as they want.

@Ray
I'm really sorry about that. Will make sure I don't repeat it.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

So, this is resolved? Can you post the resolution, please?
-craig

"You can never have too many knives" -- Logan Nine Fingers
yabhinav
Participant
Posts: 37
Joined: Wed Mar 05, 2008 11:54 pm
Location: Hyderabad

Post by yabhinav »

Resolution:
Instead of passing the entire query as a parameter I've passed only the necessary columns in one parameter and the filter conditions in another parameter. In the oracle stage i have something like

Code: Select all

select #parcolumns# from #partablename# where #parconditions#
So instead of passing a parameter with another I used multiple parameters to achieve what i wanted.
Post Reply