DSXchange

Hi Ranga, Why cannot you put CurrentDate() in the derivation part of the field. What is the need for you to go for stage variables and @date function. I don't know because I used to work with DB2 database and I don't know about Oracle OCI stage. I just wanted to make sure that you know about the Cur...

Thanks Roy! Actually if we try to run the job with DB2 API, the job runs forever and if we try to abort, the table space gets corrupted and we need to rebuild the table once again. When we consulted with ETL, he suggested to go with Enterprise stage. So I was asking if there is any option to achieve...

Hi We have a problem. We have to load a table using a user-defined insert query and we are doing it by just passing a dummy row to the DB2 plugin and triggering the insert query. Here before inserting we need to disable the redo logging for the table because the volume of insert is quite large and l...

Hi Instead of juggling with DS logic, better you use grep command and seperate the records based on the value in the first column and put the records in seperate file. Later develop jobs for these individual files. That would be a better option to do if the number of values the first column can take...

Hi Vivek It's simple and straight forward! You are having a column (non-key column) in both the datasources for the join stage. Depends on your link ordering it picks the column from the driving datasource and dropping the other column with the same name from the other datasource. Just look into tha...

Hi akrzy,
Just double-click the stage from which the link to the reject file arises (It may be a transformer or a database stage itself). Go to the column tab and find the check-box at the bottom left. Just uncheck and your problem will be solved! I don't know any other way to explain :D

Hi
Declare a parameter in the job for holding filename. From the shell script you call the job, just get the name of the file from the specified directory (since the only file in the directory is the required file), and pass it as the job parameter to the job. That solves the problem!

akrzy,

Can you approximately tell what is the volume of the data your job is going to handle? The answer will be more crisp if you provide the detail of the volume of data. But generally, what Saravanan says will be more applicable.

Hi akrzy,
As Arnd says, you need to turn off the column propagation for the reject link. That will solve the problem. Again, I raise a question here. What is the impact in the performance on turning on/off the column propagation option? Is it significant?

Rajiv It's quite simple! You can use a shell command as an after job subroutine like echo '' > File1 . Care should be taken to set the option that this command should execute only if the job completes successfully or otherwise you will lose your file. Alternatively you can also achieve this by calli...

Hi Vivek,
As described in one of the previous post, it is a better idea to keep different names for the files and after all the jobs are executed, just merge all the files using a batch script. That's a neat and simple way of doing it. Any more ways?

Vivek,

As far as I could think, it's impossible to do in DataStage because in DataStage each output file you are writing into should be determined at the time of job development. One thing I can suggest you is that it can be done using DOS batch files. Please try that and let us know the result.

Hi Nothing including one, two or three single quotes in place of one single quote is working. Is it a bug in DataStage? Is it fixed in latest version? We are using 7.0.1 ! Is there any other work around to achieve this? Craig, there is no such option called SQL file in DB2 enterprise stage. I though...

Thanks Matthieu,
But even both the slashes did not work! Any other way of doing it?

Hi All We are facing a peculiar problem for which we need a solution. We are passing an entire query to DB2 Enterprise stage as a parameter. The query has lot of conditions which includes lot of single quote characters. The problem we are having here is, whenever we try to pass the query as a parame...