Config File

[bala_135]

Hello,

I am having 2 nodes in my config file.node1, node2.When i am using node1 the job is running but when i use node2 or use both i my config file i am getting the following phantom error:-3640.Kindly help me to solve the problem.

Also please suggest me a way to view the datas in the nodes when we partition.

Regards,
Bala

[ArndW]

Could you post your config file, and also check to make sure that all the paths in Node2 actually exist and have appropriate permissions set?

[track_star]

Please post the entire error message from the log. As for seeing the data in mid-stream, you can use a peek stage. If you don't want to put all of the peek stages into the job (just to turn around and take them out later), compile the job in trace mode and run it. The GUI will insert the peeks automatically into the osh script.

[bala_135]

Hi,

My config file looks like this.
{
node "node1"
{
fastname "serv1"
pools "" "pool1"
resource disk "C:/Ascential/DataStage/Datasets" { pools "" }
resource scratchdisk "C:/Ascential/DataStage/Scratch" { pools "" }
}


}

{
node "node2"
{
fastname "serv1"
pools "" "pool1","pool2"
resource disk "C:/Ascential/DataStage/Datasets" { pools "" "pool1" "pool2"}
resource scratchdisk "C:/Ascential/DataStage/Scratch" { pools "" }
}

}

How to view the permissions set for each node?

Log looks like this:-
Nodemap node "node2" is not in the config file
Contents of phantom output file =>
DataStage Job 121 Phantom 2656

[ray.wurlod]

-3640 is not an error code; it's a process ID reported as a signed integer. "Phantom" simply means "background process" - all DataStage processes on the server are "phantom" processes.

You need to reset the job after it aborts. Look in the log for a message "from previous run...".

Check the braces in your configuration file. Does the configuration end before the definition for node2 appears?

[lstsaur]

Hi Bala_135,
For sure your configuration file is incorrect; no need a comma to separate the names of Pools and too many braces between node1 and node2.
Try the following:
{
node "node1"
{
fastname "serv1"
pools "" "pool1"
resource disk "C:/Ascential/DataStage/Datasets" { pools "" }
resource scratchdisk "C:/Ascential/DataStage/Scratch" { pools "" }
}
node "node2"
{
fastname "serv1"
pools "" "pool1" "pool2"
resource disk "C:/Ascential/DataStage/Datasets" { pools "" "pool1" "pool2"}
resource scratchdisk "C:/Ascential/DataStage/Scratch" { pools "" }
}
}