DSXchange

You need to have right administrator, both Unix, and IBM Websphere DataStage to have the environment setup. By the time your environments are set you need to read some documentation, have some training etc.

Hi All, I have a wierd situation. I have a job which is mapped from one source on AS-400 DB2 using ODBC stage. The target is Teradata Enterprise Stage Plugin. This is a simple one to one mapping without any conversions. The source stage shows data while we do view data. The job starts and the ends w...

You got a right answer, a transformer with 2 outputs will do the job, selecting the right metadata... Use 2 links writing to the same dataset Hi All, Thanks ucf007, Eg. Source columns A B C D E Source records 123 AAA 2354 4656 bbb 234 BBC 8762 9876 ddd Target columns A B C D E Target Records 123 235...

Go to director. Use Job---->Cleanup Resources. Look for the process associated to your job, and press logout button there. This will release your jobs which are locked thru that process number.
Also you can kill the process from the unix command line.

I tried to understand what you are trying to achieve using an ETL tool. This is a report kind of structure which you are trying to get using DataStage. I do not say it is impossible, but please note that Datastage is not meant to produce reports, inturn it does ETL. You are trying to present a repor...

You can make this happen through the sequencer job control. Create a parameter file which contains the date to be tagged to the table/database names. Have this parameter in the job as well as in the sequencer. Do proper parameter mappings in the sequencer for any such job which has a changing table/...

Put proper parameters what you do in jobs, the same way, and compile the sequence. copy the sequence compiled code and paste it in a new server job control script, check for '# #' in the code and remove it manually. Then compile that new server job. and instead of running the sequencer, run this new...

You can wrap the stored procedure in a shell and call the shell in the after job subroutine to execute that shell which has that stored procedure wrapped with it.

or
you can call that procedure in your target OCI , SQL's after tab in the same job which creates that table.