Would be interesting to see if DataStage 8.0 has that.
Sequence Job: Auto Matching of Parameter in the Job Activity
-
I_Server_Whale
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
DataStage 8.0 does not have that.
What is does have is a new object called a "parameter set" - literally a named collection of parameter definitions, so you can load that instead of the individual parameters. Makes life a lot easier! You can also select from the list of parameters in the set to effect a partial load, much as you can with column definitions when loading a table definition or jobs when importing DataStage components.
What is does have is a new object called a "parameter set" - literally a named collection of parameter definitions, so you can load that instead of the individual parameters. Makes life a lot easier! You can also select from the list of parameters in the set to effect a partial load, much as you can with column definitions when loading a table definition or jobs when importing DataStage components.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I wrote my own. When I wrote Parameter Navigator it became difficult to fix all the sequences. We had 500 jobs and over 100 sequences. Each job added at least 3 parameters for each database touched. I wrote one job to fix all ODBC jobs. So I fixed one job for each database touched. Next I copied all the parameters for that job plus I copied the one ODBC stage fields for DSN, User and password to the new stages. The job would search for that database name in all jobs and then fix them.
For example if "BEATLES" was your DSN name. I wanted jpSourceDsn, jpSourceUser and jpSourcePwd parameters to be used for this connection. You not only need these 3 parameters copied but you need #jpSourceDsn# in the ODBC stage. Once you got all of these fixed you need the sequence to have these 3 parameters and you need them automatched into the job activity.
If you add parameters to a job then the sequence automatically adds them to the job activity. Automatching 500 jobs in 100 sequences could take days or weeks. This automatch job by itself pays for Parameter Navigator. It took a while to figure out how they stored these values in a sequence job. You get all these jobs and a lot more with PNav but you can do it the hard way if you want. You get complete source on these jobs too.
For example if "BEATLES" was your DSN name. I wanted jpSourceDsn, jpSourceUser and jpSourcePwd parameters to be used for this connection. You not only need these 3 parameters copied but you need #jpSourceDsn# in the ODBC stage. Once you got all of these fixed you need the sequence to have these 3 parameters and you need them automatched into the job activity.
If you add parameters to a job then the sequence automatically adds them to the job activity. Automatching 500 jobs in 100 sequences could take days or weeks. This automatch job by itself pays for Parameter Navigator. It took a while to figure out how they stored these values in a sequence job. You get all these jobs and a lot more with PNav but you can do it the hard way if you want. You get complete source on these jobs too.
Mamu Kim