using Environment Variables in Trigger Expression
Posted: Tue Jul 24, 2007 2:27 pm
Hi,
I am facing a problem, like this:
The job design is this Job Design.
Now the sequence has 2 environment variables, $APEPMSYNCH and $AMEPMSYNCH.
I am testing for the values of these variables on the trigger link of Nested Condition stage,
"AP_EPM" and "AM_EPM".
Now, when I compile the job sequence only, it does not complain for for any error.
When the sequence is getting compiled by "Multiple Job Compile", the sequence gives err for $AMEPMSYNCH & $APEPMSYNCH not defined.
But when I compile ONLY this sequence , again using Multiple Job Compile it gets compiled well.
I dont know what is wrong and where ?
I have tried using a normal Job parameter on the trigger link expression, but that also behaves the similar way.
is it like that we cannot use any Environment or job params in the trigger expression ?
Alternatively, please suggest some workarounds ..
Thx
I am facing a problem, like this:
The job design is this Job Design.
Now the sequence has 2 environment variables, $APEPMSYNCH and $AMEPMSYNCH.
I am testing for the values of these variables on the trigger link of Nested Condition stage,
"AP_EPM" and "AM_EPM".
Now, when I compile the job sequence only, it does not complain for for any error.
When the sequence is getting compiled by "Multiple Job Compile", the sequence gives err for $AMEPMSYNCH & $APEPMSYNCH not defined.
But when I compile ONLY this sequence , again using Multiple Job Compile it gets compiled well.
I dont know what is wrong and where ?
I have tried using a normal Job parameter on the trigger link expression, but that also behaves the similar way.
is it like that we cannot use any Environment or job params in the trigger expression ?
Alternatively, please suggest some workarounds ..
Thx
