DSXchange

I tried it again and this time is worked fine. So I think the issue was something else - might be with some services.

We rebounced the server and it is working fine. I think the issue was with WebServer according to admins. Not sure if my import caused it or something. I am going to try the reimport and see if I can reproduce the error.

I have tried this one as well. But now I am not able to log onto DS project itself and so can not try import.

Hi, I exported a routine and a job that uses this routine from the 7.5 project from server 1. I wanted to use this on another server which is V8 DataStage. I started the import and it failed with some errors. Actually I did not record the errors. After the import DS repository was not showing anythi...

Here is one approach:

Generate first CustNo col with 50 columns for dates and then use the pivot stage to get 50 rows for the same customer.

Have you tried search option? I have seen this question sometime back. If you do a search might give you answer quickly than waiting.

what are you trying to achieve? If you could tell what functionality you are trying, you might get a proper solution.

Another option is create your own version of UtilityJobRun. In it, get the status of the job before calling DSRunJob. If needed, run the reset command for the job.

Why dont you try something like below? 1. A row generator generating the values you want in IN query. Or a Seq file containing the IN list - one two for each value. 2. A Sparse lookup (if the IN list is small, otherwise join) on the table from on which you wanted to run IN query 3. On the output do ...

Few months back we also has the same problem and we change then no. of nodes for that job from 2 to 4 to solve the problem.

It has been working fine so far.

Are you getting any warning or error message in the logs when the job finishes?

Try function like NullToValue or set the file properties for null handling.

If you do not want these 200 records to be the part of before set then you can create an extract job and store this before set to a dataset. Then you can use this dataset for this process.

I have never created one, but have read something about it. May be defining a Property for build op and then setting this property to job parameter should solve your problem.

Ashis,

For one type of pivoting there is stage provided by DataStage as pivot. Try that. For the other you have to use transformer and then aggregation.

If you search you will get many post which discuss this.

This is just fantastic. I encountered the problem today. My job compile was failing with error - project space not there. I saw the similar file and was just wondering could I find something on this filename which is taking 1.5 GB of space.

DSX is great place and a life saver for DS users