Warning: Configuration file not set

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
anand_dafaria
Premium Member
Premium Member
Posts: 36
Joined: Wed Dec 27, 2006 3:50 am
Location: Phoenix

Warning: Configuration file not set

Post by anand_dafaria »

Hi All,

Configuration file option which comes in the Advanced Tab properties. The "configuration file" drop down menu option and "Node map constraint" both are greyed out. I cheked in the administrator that APT_CONFIG_FILE is also set, but couldn't figure out how to activate those options which are greyed out.

We have a CFF stage which we need to run sequentially while reading the data. But once the data is read we want to execute the remaining stages in parallel. So for remaining stages we wanted to give four node option to perform, but with thise options greyed out we are left with no choice but to run the stages sequentially.

I think it makes some sense. :?:

Anand
LenGreenwood
Premium Member
Premium Member
Posts: 37
Joined: Mon Dec 08, 2008 4:02 am
Location: Milton Keynes, UK

Post by LenGreenwood »

If the "Execution mode" box on the Advanced tab says "Parallel", the stage will run in parallel. The number of nodes it uses depends on the config file it is given at run time, not design time (that's what the $APT_CONFIG_FILE parameter gets used for).

The bit of the Advanced tab that says "configuration file"
shows the name of the configuration file that the system is currently using - it changes if you have a $APT_CONFIG_FILE parameter declared for the job. But that bit of the form only gets enabled if the current config file has node pools declared in it. You don't really need node pools just to run part of your job in parallel - that happens automatically for the stages that are not constrained to run sequentially.
Post Reply