8/17/2019 Configuration File Final

1/14

© 2009 Wi ro Ltd - Confdential

Confguration File

-Prepared ByHimanshu Thakkar

8/17/2019 Configuration File Final

2/14

© 2009 Wi ro Ltd - Confdential2

Contents

Create/Edit Confguration File2

Set Confguration File at Projet !e"el

#

Features o$ Confguration File%

Confguration fle struture&

Confguration File $or 'PP/Cluster/(rid7

Confguration fle $or simple S'P

)

Set Confguration File at *o+ !e"el,

8/17/2019 Configuration File Final

3/14

© 2009 Wi ro Ltd - Confdential3

Features o Confguration File

• The Datastage configuration file is a master control file for Datastage jobswhich describes the parallel system resources and architecture.

• The configuration file provides hardware configuration for supporting sucharchitectures as SMP (Single machine with multiple CP ! shared memoryand dis"#! Grid , Cluster or MPP  (multiple CP! multiple nodes anddedicated memory per node#.

•  The main outcome from having the configuration file is to separatesoftware and hardware configuration from job design. The main use ofconfiguration file is to change nodes and control processes at run time.

• $ job can utili%e different hardware architectures without being recompiled.

•  The Datastage configuration file is specified at runtime by a$APT_CONFIG_FILE variable.

8/17/2019 Configuration File Final

4/14

© 2009 Wi ro Ltd - Confdential4

Create/Edit Confguration File

 To change or create a new configuration file &

• 'o to Designer Client

• 'o to Tools

• Select Configurations

• Select the Configuration ile to edit or create a new then save and chec".

•The easiest way to validate the configuration file is to e)port $PT*C+,-'*-/ variable pointing to the newly created configuration fileand then issue the following command& orchadmin chec 

 $fter creating a new Configuration ile we can set it at two levels Projectevel and 0ob evel.

8/17/2019 Configuration File Final

5/14

© 2009 Wi ro Ltd - Confdential5

Contd

8/17/2019 Configuration File Final

6/14

© 2009 Wi ro Ltd - Confdential!

"et Confguration File at #ro$e%tLe&elTo set configuration file at project level&

• 'o to $dministrator Client.

• Select the Project for which Configuration file is to be set.

• 'o to 'eneral Properties.

• Select Parallel 1ode.

•  Set the value for $PT*C+,-'*-/ parameter with the path ofnewly2already created Configuration file.

+nce we set this parameter! Datastage will follow the same path by defaultfor Configuration ile for all the jobs of that project.

8/17/2019 Configuration File Final

7/14

© 2009 Wi ro Ltd - Confdential7

"et Confguration File at 'o( Le&el

 To set configuration file at job level&

• 'o to Designer Client.

• +pen the job for which Configuration file is to be set.

• 'o to 0ob Properties.

• Select Parameters.

• $dd /nvironment 3ariable.

• Select 4$PT*C+,-'*-/ parameter and set the value with the path ofnewly2already created Configuration file.

8/17/2019 Configuration File Final

8/14

© 2009 Wi ro Ltd - Confdential)

Confguration fle or a si*ple"+# 

8/17/2019 Configuration File Final

9/14

© 2009 Wi ro Ltd - Confdential9

Confguration File "tru%ture

ollowing are the different components in any Configuration ile&

•Node

•Pool

•Fastname

•!esource "is

•!esource Scratch "is

8/17/2019 Configuration File Final

10/14

© 2009 Wi ro Ltd - Confdential,0

Contd

Node •-t is a logical processing unit.

•/ach node in a configuration file is distinguished by a virtual name anddefines a number and speed of CPs! memory availability! page and swapspace! networ" connectivity details! etc.

•5ithin a configuration file! the number of processing nodes defines the

degree of parallelism and resources that a particular job will use to run.

• $ configuration file with a larger number of nodes generates a largernumber of processes that use more memory (and perhaps more dis"activity# than a configuration file with a smaller number of nodes.

•5hile the DataStage documentation suggests creating half the number ofnodes as physical CPs! this is a conservative starting point that is highlydependent on system configuration! resource availability! job design! andother applications sharing the server hardware.

8/17/2019 Configuration File Final

11/14

© 2009 Wi ro Ltd - Confdential,,

Contd

Fastname The fastname is the physical node name that stages use to open

connections for high volume data transfers.

• Typically! you can get this name by using ni) command 6uname 7n8.

• -n S1P ! it is the principal node name as all nodes uses same fastname .

Pool•  9ased on the characteristics of the processing nodes you can groupnodes into set of pools.

• $ pool can be associated with many nodes and a node can be part ofmany pools.

• $ node belongs to the default pool unless you e)plicitly specify a poolslist for it! and omit the default pool name (:;# from the list.

8/17/2019 Configuration File Final

12/14© 2009 Wi ro Ltd - Confdential,2

Contd

• !esource dis &

8/17/2019 Configuration File Final

13/14© 2009 Wi ro Ltd - Confdential,3

Confguration fle or a +##

8/17/2019 Configuration File Final

14/14

Thank ou