Unable to parse Configuration file

[dsean]

Hi all,
I have a configuration file with 4 nodes and I set it up in Administrator. In my job , I am using a special token $PROJDEF as a default value for the Configuration file.

Now I want to constraint the Sequential file stage in my job to run it on a single node. But I am getting a message in Sequential File --> Advanced tab saying "Unable to parse the Configuration file" and the node map constraint is disabled. Please give me some advice on how to handle this.

Thanks in Advance
Sean

[ray.wurlod]

Switch back temporarily to a hard-coded pathname as the value of $APT_CONFIG_FILE. When you're done testing reinstate $PROJDEF as the default value.

[sagar deshmukh]

Hi
I am also getting same warning... in OCI stage....
What can be done to remove it...
What will happen if i ignore it?

[chulett]

Please start your own post with the relevant details of your particular version of this problem.

[datisaq]

But sequential file stage by default runs in sequential mode, then why you need to constraint it on a single node?

[adityamohanty]

Hi All,
As far from my experience,If We check Execution Mode to "Sequencial Mode"then we can able to run our job in a single node, as in Parallel by default this option is in "Parallel Mode" only.If I am wrong then please let me know.

[adityamohanty]

Hi All,
As far from my experience,If We check Execution Mode to "Sequencial Mode"then we can able to run our job in a single node, as in Parallel by default this option is in "Parallel Mode" only.If I am wrong then please let me know.