APT Config File
Moderators: chulett, rschirm, roy
APT Config File
Hi
We are having three different versions of APT Config file and we are passing different file name as a parameter to different job based on the job complexity. Here the issue is, whenever I try to compile the job having a parallel transformer, without giving default value in $APT_CONFIG_FILE parameter, the job doesn't compile and says that the value is required for compilation. So what I am afraid for is, will this default value will be overridden when I pass some other APT Config file name from the calling shell script ?? Or will it set at the compilation time itself which cannot be changed during run time ??
Kindly help me out in this regard.
DataStage PX version : 7.0
OS : IBM AIX
Thanks,
Vignesh.
We are having three different versions of APT Config file and we are passing different file name as a parameter to different job based on the job complexity. Here the issue is, whenever I try to compile the job having a parallel transformer, without giving default value in $APT_CONFIG_FILE parameter, the job doesn't compile and says that the value is required for compilation. So what I am afraid for is, will this default value will be overridden when I pass some other APT Config file name from the calling shell script ?? Or will it set at the compilation time itself which cannot be changed during run time ??
Kindly help me out in this regard.
DataStage PX version : 7.0
OS : IBM AIX
Thanks,
Vignesh.
Re: APT Config File
I come from the regular DS world. In the regular DS the values you pass from the shell scripts overwrite the default values and I am assuming the same would happen with PX also and that would be a safe assumption I would say...
-
- Participant
- Posts: 75
- Joined: Tue May 13, 2003 4:14 am
- Location: California
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Not saying that at all. What I'm saying - all I'm saying - is that, when the job is compiled, it needs to generate an object that can be cloned across multiple processing nodes.
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.