We have some params defined in the project definition. We use those in our job by using $ qualifier.
It works fine for stages like sequential file, DB stage. But it seems it do not work for Px Tansformer derivation. We get complilation error if system variable is used in the Px derivation.
Can someone explain me, what setting we need to have project wide so can use 'System Environment Variables' in the transformer?
Thanks in advance.
Projdef vars in Px transformer - compilation error
Moderators: chulett, rschirm, roy
Projdef vars in Px transformer - compilation error
Thanks with regards,
videsh.
videsh.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Are you using the expression editor to build the expression in the Transformer stage?
Environment variable job parameters should (do) work perfectly well in parallel Transformer stages.
Can you post one of your expressions?
If you're not using the expression editor, can you please do so and note whether the expression thus produced is different from the one that is not working? (And let us know.)
Environment variable job parameters should (do) work perfectly well in parallel Transformer stages.
Can you post one of your expressions?
If you're not using the expression editor, can you please do so and note whether the expression thus produced is different from the one that is not working? (And let us know.)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
In the transformer, at derivation we just mention the 'System Environment Variable'. Say parameter user is defined with PROJDEF, then it is sourced in at Job parameter as, $user. In the transformer derivation for this particular coulmn, mapping derivation is just $user.
It gives error only after, we compile the job.
It gives error only after, we compile the job.
Thanks with regards,
videsh.
videsh.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Can you post one of your expressions?
Please also verify that the default value for the job parameter (in the job properties) is $PROJDEF, not PROJDEF.
Does this occur if the default value is something else?
And, while you're testing, can you also try the default value $ENV ?
Please also verify that the default value for the job parameter (in the job properties) is $PROJDEF, not PROJDEF.
Does this occur if the default value is something else?
And, while you're testing, can you also try the default value $ENV ?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.