Page 1 of 1

Environment variables

Posted: Tue May 05, 2009 9:52 am
by Manfred Hagedorn
Hello,
i want to use an environment variable in a parallel job.
I have defined a user-defined variable in the Administrator.
When i use this variable in a parallel job as a Parameter and set default to "$PROJDEF" it works!
But when calling this job by a sequence i don't know whether:
- the sequence should hand over an empty field to the job for this field
- or should i define the same variable on sequence level as well and then hand over it to the job
- if yes, should i set the default value on sequence level as well to "$PROJDEF" ?

I think, i have tried all cases ... didn't find the right way.
Hope anybody can help me.
Thanks a lot in advance.
Manfred

Re: Environment variables

Posted: Tue May 05, 2009 10:04 am
by sachin1
sorry dear but please post the message in parallel section.

Re: Environment variables

Posted: Tue May 05, 2009 10:09 am
by nagarjuna
When your are using some parameters in the job those parameters need to be passed from sequence which is using that job .Otherwise default values specified in the job will be considered .


In sequence give whatever parameters that is being used in job and map in the activity stage .If you want to take value from administrator then define $PROJDEF and map into the job .


Manfred Hagedorn wrote:Hello,
i want to use an environment variable in a parallel job.
I have defined a user-defined variable in the Administrator.
When i use this variable in a parallel job as a Parameter and set default to "$PROJDEF" it works!
But when calling this job by a sequence i don't know whether:
- the sequence should hand over an empty field to the job for this field
- or should i define the same variable on sequence level as well and then hand over it to the job
- if yes, should i set the default value on sequence level as well to "$PROJDEF" ?

I think, i have tried all cases ... didn't find the right way.
Hope anybody can help me.
Thanks a lot in advance.
Manfred