Default Configuration file

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
vsusmita
Participant
Posts: 4
Joined: Thu Aug 04, 2005 7:21 am

Default Configuration file

Post by vsusmita »

Hi,

I have accidentally deleted default configuration file, can some body please help me how to generate/create the default configuration file..

Thanks in advance
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Welcome aboard. :D

The default configuration file consists of two nodes, which you can call Node0 and Node1 (or anything else you like).
The fastname is the name of the machine where DataStage is installed.
Each node is only in the default node pool only.
Each has one (the same) disk and scratch disk resource, being the pathname of the appropriately named folder within the DataStage Engine directory (e.g. /usr/Ascential/DataStage/DSEngine/Scratch for the scratch disk resource).

The default configuration file should be called default (from the configuration editor) or default.apt (from vi). It is stored as default.apt but the configuration editor adds the suffix for you.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
vsusmita
Participant
Posts: 4
Joined: Thu Aug 04, 2005 7:21 am

Re: Default Configuration file

Post by vsusmita »

Thanks Ray, could some one please post the default configuration file ,
so i cam modify and use it..
and what is pool ...

Thanks,
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Please read the chapter on Configuration Files in the Manager guide. This will aid your understanding, and give you examples.

I do not have access to DataStage until mid-May, so am unable to post any examples. Maybe someone else will post the default.apt file from a UNIX installation.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
heman
Participant
Posts: 2
Joined: Fri Apr 21, 2006 10:39 am

Re: Default Configuration file

Post by heman »

$ more default.apt
/* default - Default Configuration file


This Configuration file has 1 processing node
on DataStage Server psaeux002,(devtest_node1)
and DB2 Server psadux001 (psadux001).

*/
{
node "devtest_node1"
{
fastname "psaeux002"
pools ""
resource disk "/worknode1/datasets/" {pools ""}
resource disk "/worknode2/datasets/" {pools ""}
resource disk "/worknode3/datasets/" {pools ""}
resource disk "/worknode4/datasets/" {pools ""}
resource scratchdisk "/worknode1/scratch" {pools ""}
resource scratchdisk "/worknode2/scratch" {pools ""}
resource scratchdisk "/worknode3/scratch" {pools ""}
resource scratchdisk "/worknode4/scratch" {pools ""}
}
node "psadux001"
{
fastname "psadux001"
pools "DB2"
resource disk "/worknode/datasets" {pools ""}
resource scratchdisk "/worknode/scratch" {pools ""}
}
}
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

That's not a good example of a default configuration file, since not all nodes are in the default node pool. Also, in the default configuration file, the disk and scratch disk resources are subdirectories in the DS Engine directory. (And it is undocumented.)

Based on that, however:

Code: Select all

{ 
   node "node0" 
   { 
   fastname "dsserver" 
   pools "" 
   resource disk "/usr/Ascential/DataStage/DSEngine/Data/" {pools ""} 
   resource scratchdisk "/usr/Ascential/DataStage/DSEngine/Scratch/" {pools ""} 
   }

   node "node1" 
   { 
   fastname "dsserver" 
   pools "" 
   resource disk "/usr/Ascential/DataStage/DSEngine/Data/" {pools ""} 
   resource scratchdisk "/usr/Ascential/DataStage/DSEngine/Scratch/" {pools ""} 
   } 
} 
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply