DSXchange

AS to the time "change", looks like whatever is hosting the web service has not adjusted for daylight saving. Or there's a really weird bug in the exception handler.

Edit the extended properties (Edit Row...) and provide Field Width property values.

It may not make sense to you, but it's the technique we use to prevent insertion by the framework of unnecessary tsort operators. If you don't like it, then don't complain about the performance hit taken because of the inserted tsort operators resorting already-sorted data.

I need help on urgent basis and i would be greatful if you can provide me the solution. Etiquette Note We don't do urgent here. We are all volunteers, no-one is paid for posting. If you want urgent, sign up for premium service with your support provider, and learn the true cost of urgent. As for "p...

That code is bad from a number of perspectives. I do hope you're not claiming authorship. What do you do with ReportType? Where do you call DSMakeJobReport? Why didn't you format the code and enclose it in Code tags?

Welcome aboard. :D

Etiquette Note
We do not hijack threads. Your question is unrelated to the topic of this thread. Please choose Post New Topic in the appropriate forum (Server or Parallel).

The answer will be different depending on what job type you are using.

In Designer, select New > Data Migration Job

I believe you're on the wrong track, and have encountered a timing issue when there were no licences available for the compiler, but attributed that to your constraint. Search the forum for other instances of "no license available".

No.

If you don't put in a Sort stage, DataStage will insert tsort operators, because the Join stage requires sorted inputs. If you have an ORDER BY clause, you can make the Sort stage specify "don't sort (already sorted)" so that it does nothing, but the existence of the Sort stage will prevent DataStag...

If your job design takes all three links into a single ODBC stage then you can use the Transaction Grouping feature of that stage. Transformer stage allows you to control output link execution order, so that's not where the problem arises. Whether it waits or not is largely a factor of whether row b...

Welcome aboard. :D

This is too vague a pair of questions to answer here. There is a vast array of error handling capabilities in DataStage.

The question about third-party tools smacks very much of an interview question. The short answer, because of your "in DataStage" phrase, is none.

You appear to be confused. At least you've confused me. You are using user-defined SQL to interrogate a text file? Is this perhaps via an ODBC stage referring through an ODBC driver for text files? A smarter mechanism would be to read the entire file into your job using a Sequential File stage, then...

The repository ought to be of no interest whatsoever for a business analyst. It does not affect how the business is analyzed. (Of course the BA may simply be curious.)

Check that the column really IS Char(1) in Oracle, not Char(4). Debug the job, and view the actual data values being selected. Does any of them have more than one character? If the error message includes a row number (or if you trap the input row number on the reject-handling link), you can go strai...