Multiple source files single ETL

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

anu123
Premium Member
Premium Member
Posts: 143
Joined: Sun Feb 05, 2006 1:05 pm
Location: Columbus, OH, USA

Post by anu123 »

rasi wrote:Anu

Once you made your Job as Muliti Instance job then if you go and open your Sequencer job you will have Invocation Id tab under Job name. This is the place where you need to type in the invocation id for each instance. hope this helps
thanks much siva.
I got it....

I ran the sample ETLs successfully.

thank you all once again
Thank you,
Anu
balajisr
Charter Member
Charter Member
Posts: 785
Joined: Thu Jul 28, 2005 8:58 am

Post by balajisr »

chulett wrote:One big problem with this approach - jobs have a 'User Status' area, routines don't. Besides, if you've already got a delimited string of all the values, do you really need to go to all that ef ...
Craig,

That's correct when you already have the list of file values you do not need userstatus and you can directly hardcode the values in the start loop activity stages or put into uservariable and access it in start loop activity.
i did not understand anu's problem correctly. I assumed that the list of filenames is generated in the previous job and the list of files can be of any number.sorry for that.

Suppose in the previous job i create a comma delimited string with the list of file names, Is there any better way i can pass the comma delimited string to the uservariable or to start loop activity in the job sequence without using user status?
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

There's nothing wrong with the User Status approach - as long as you understand the pros and cons.

I've also created a flat file with values like that inside a job and then built a routine that basically echoes it back to standard out and captures that. Run the routine directly in the User Variables stage and you are all set.

Many ways to solve this particular puzzle.
-craig

"You can never have too many knives" -- Logan Nine Fingers
balajisr
Charter Member
Charter Member
Posts: 785
Joined: Thu Jul 28, 2005 8:58 am

Post by balajisr »

chulett wrote:There's nothing wrong with the User Status approach - as long as you understand the pros and cons.

I've also created a flat file with values like that inside a job and then built a routine that basically echoes it back to standard out and captures that. Run the routine directly in the User Variables stage and you are all set.

Many ways to solve this particular puzzle.
Great. Thanks Craig.
Post Reply