Providing parameters to all the jobs/Selective jobs

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
mdbatra
Premium Member
Premium Member
Posts: 175
Joined: Wed Oct 22, 2008 10:01 am
Location: City of London

Providing parameters to all the jobs/Selective jobs

Post by mdbatra »

Hi,
I am defining user-defined variables in administrator. I need to set these variables for all the jobs/Selective jobs in a project, in a single shot, rather than adding from job properties parameters tab.
Any prefered approach !
Rgds,
MB
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Do you mean environment variables?

The answer is to use parameter sets.

To do that, you will need to upgrade to version 8. Until then there is no "all in one shot" solution.

Another possibility is custom coded "read parameters from a file" functionality, perhaps in job control routine.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
sureshreddy2009
Participant
Posts: 62
Joined: Sat Mar 07, 2009 4:59 am
Location: Chicago
Contact:

There is no solution for one shot of variables in 8.0

Post by sureshreddy2009 »

ray.wurlod wrote:Do you mean environment variables?

The answer is to use parameter sets.

To do that, you will need to upgrade to version 8. Until then there is no "all in one shot" solution.

Another possibil ...
hi
after adding variable in administrator there is no solution to add at a shot up to 8.0,but simpler thing is at the time of development add the variables in all/selective jobs through add environment variables tab and set $PROJDEF to those variables after that instead of changing every time in administrator at the time of sequence running write one script in unix which will display all the required parametersfrom a file and take executesh stage in sequencer and in that call the unix script and following that in each and every job activity write function to read those variables
Suresh Reddy
ETL Developer
Research Operations

"its important to know in which direction we are moving rather than where we are"
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Wow, that's one long sentence... and not a period in sight. :wink:
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply