Config File

devanars · Post by **devanars** » Thu Aug 27, 2009 9:32 am

If i run the job with 2 node config file,the job is running with single node only. i have created 2 node file like this
{
node "node1"
{
fastname "a"
pools ""
resource disk "/opt/IBM/InformationServer/Server/Datasets" {pools ""}
resource scratchdisk "/opt/IBM/InformationServer/Server/Scratch" {pools ""}
}
}

{
node "node2"
{
fastname "a"
pools ""
resource disk "/opt/IBM/InformationServer/Server/Datasets" {pools ""}
resource scratchdisk "/opt/IBM/InformationServer/Server/Scratch" {pools ""}
}
}

do i need to modify anything?

chulett · Post by **chulett** » Thu Aug 27, 2009 9:43 am

First off, did you actually add the $APT_CONFIG_FILE parameter to the job and point it to your new 'two node' file?

miwinter · Post by **miwinter** » Thu Aug 27, 2009 9:45 am

Is there a method of proving said config file still (as in v7.x) through Manager or it's new equivalent? (Though for the record it looks fine and I think Craig's hit the nail on the head).

devanars · Post by **devanars** » Thu Aug 27, 2009 9:54 am

Hey I am executing the job with $APT_CONFIG_FILE parameter with two node. that is sure. do we need to validate the file if we create it as brand new.

chulett · Post by **chulett** » Thu Aug 27, 2009 10:12 am

You don't "need" to if you're thinking it won't work somehow before you do that, but it certainly couldn't hurt to have that as a standard step.

devanars · Post by **devanars** » Thu Aug 27, 2009 10:25 am

So how can i get execute the job with two/three nodes like that.

chulett · Post by **chulett** » Thu Aug 27, 2009 10:40 am

By fixing your config file. Go to Designer / Tools / Configurations, load it up and then press 'Check'. (you've got too many curly braces in your file, btw)

ray.wurlod · Post by **ray.wurlod** » Thu Aug 27, 2009 4:32 pm

The fastname must be a genuine node name, ideally the one on the fastest connection to that machine. Do you really have a node called "a"?

hiral.chauhan · Post by **hiral.chauhan** » Thu Aug 27, 2009 5:25 pm

ray.wurlod wrote:The fastname must be a genuine node name, ideally the one on the fastest connection to that machine. Do you really have a node called "a"? ...

By node name do you mean server name?

ray.wurlod · Post by **ray.wurlod** » Thu Aug 27, 2009 6:48 pm

Let's just stay with "network node name" for now - "server" is ambiguous in the current context.

Network node names occur in the hosts file or are decodable through services such as DNS (domain name service). It depends on your particular installation, and is not part of DataStage.

In your case, I suspect that the fastname needs to be the network node name of the machine on which DataStage server components, particularly the parallel engine, are installed.