Parameter

[dslisa]

Hi,
I have jobs that get their parameter from a UNIX file at runtime. These files are designed to accomodate the changing values of different environments. The values of these files should override whatever the value is defined at job level. But lately this is not happening. Somehow the values are not being passed at runtime. I have tried defining those values as $PROJDEF, as environment variable, as just regualr parameters, but nothing seems to work. Does anyone have any idea what might be the problem?
Thanks

[chulett]

No, seeing as you haven't really given us much to go on. How, exactly, do these file values get read and passed as parameters to your jobs?

[Nagaraj]

May be they are using some kind of awk commands to read the parameter file which gets the parameters in the job running script.
this is a typical scenario.

But this should take the parameters correctly...are you getting any warning or errors?

[Romy]

Hi

Sometimes if you are geiven the default parameters in your job as 4, but you need only three parameters and pass only those 3 parameters from the UNIX script, then it wont work fine. Check the name of the parameter that you given in the parameter tab with that of the unix script. it is case sensitive.

Thanks...
Romy

[Romy]

Hi

Sometimes if you are geiven the default parameters in your job as 4, but you need only three parameters and pass only those 3 parameters from the UNIX script, then it wont work fine. Check the name of the parameter that you given in the parameter tab with that of the unix script. it is case sensitive.

Thanks...
Romy

[dslisa]

Hi,
Everything is consistent. Names, value.Still cannot figure out.

[loe_ram13]

Hi,
Can you type the command you are using for sending parmeters through unix and also mention the total parameters(name and expected value) used in your job.This can make things easy to give proper suggestion.