passing a hard coded filter condition for a job parameter

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

Post Reply
cparru
Participant
Posts: 24
Joined: Wed Mar 07, 2007 11:22 am

passing a hard coded filter condition for a job parameter

Post by cparru »

Hi,

I am passing a hard coded filter condition to the job parameter and there by using it as a constraint in the transformer stage. but it is giving an error saying missing =..

the actual condition is

linkname.columnname=2 AND (linkname.columnname=\'A\'OR linkname.columnname=\'M\')

even the simple linkname.columnname=2 is also not working throwing the same error.

Any help!

Thanks,
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post by qt_ky »

The parameter can hold a value like A or M but not so much code, I don't believe, because the Transformer code must be compiled before the job is run (before the parameter is resolved).
Choose a job you love, and you will never have to work a day in your life. - Confucius
vmcburney
Participant
Posts: 3593
Joined: Thu Jan 23, 2003 5:25 pm
Location: Australia, Melbourne
Contact:

Post by vmcburney »

The Transformer stage will never accept a column name from a job parameter. You can only pass in Values and Constants, not column names. The easiest way to pass in an entire constraint including the column name is to use the Filter Stage. Some of the specialised parallel stages such as Filter and Modify can use run time column names. With the filter stage your entire Where Clause can be a job parameter.
Post Reply