DSXchange

DataStage writes two files, executes QS job (through UNIX command in after-stage subroutine perhaps). Another DataStage job reads the output file produced by QS. DataStage writes one file to disk, and streams the other into a QS job through the plug-in. I have not tried this approach, but theoretica...

Exactly the opposite. Only one input stream is presently permitted.

At the top of this page there is a small menu. One of the options is Search. Click it.

Is this reliably reproducible? If so, the answer to your question is probably yes, and you need to report it to your support provider. You might also try installing more memory in your client machine.

The "fractional truncation" message is generated by SQL Server (you can discern this from the square bracketed information in the message). It may be that SQL Server has some data with more than two decimal places and warns about the truncation when delivering a DECIMAL(x,2). It may also be that the...

If the largest length is 900, then searching for those with length > 1200 would be expected to return zero rows. The result is correct!

-1 means "bad handle" - they are perhaps trying to test the routine rather than calling it from a job.

The import process will "guess" the data type, precision and scale from your data. You can amend any wrong guesses as part of the import wizard, before actually saving the table definition into the Repository.

"Pos arg" = "positional argument" The message is telling you that some function you are using has more positional arguments than can be filled from your row, because there are fewer fields in your record schema than the number of arguments. Now you have to do some detective work to figure out where ...

Is this a delimited or fixed-width file?

Is FMT function available in parallel jobs?

View Data does not check metadata.

Running a job does perform a metadata check, so it can issue metadata mismatch warnings.

So the answer to your question is YES.

Please go back to your very expensive consultants and ask about restart recoverability. Landing data can be part of a good design, for example if you have different time windows available for extraction and for loading. Sure you sacrifice some throughput time when compared to not landing data, but y...

I've also seen this. I think it's related to the mouse brand; some work, some don't. No idea why. But it's frustrating when you're used to the scroll wheel!

Post the precise sort command that you have used in the Execute Command activity as well as the (already requested) error message, and a more precise diagnosis is likely to be possible.