DSXchange

Vino_joe84 wrote:we cannot run the parallel version here.

What do you mean by this comment? You have posted in the parallel jobs forum, and are discussing parallel job stage types.

The report says It has updated 8 records intead of 4 records, but when seen in the database it shows that it has updated 4 records only... That's where you are wrong. The report says that eight rows were sent to the database. Whether or not these succeeded in updating existing rows is not what is b...

The examples in the manual (Pivot.pdf) are very clear. Essentially the input and output tabs carry the appropriate column definitions. The stage properties identify the pivot key, non-key non-pivoting columns (if any) and the pivoting column names, as a comma-delimited list.

The DataStage log reports what DataStage did.

It can be done in a Filter stage. The stage will have two outputs, one constrained by an appropriate WHERE condition, the other to handle the "otherwise" condition.

Welcome aboard.

When's the interview?

I suggested two solutions. You can get a premium membership which will allow you to read them. Premium membership is one of the ways that DSXchange is funded. All revenue from premium memberships is devoted to defraying the hosting and bandwidth costs incurred by DSXchange. By taking premium members...

No surprise about 10 rows yielding 10 identical file names; you look at the first file first - unless it has fewer than 10 rows that's exactly what I'd expect to see. You could change the sampling and skip on View Data to see what I mean.

"some path error" is not very helpful.

Always post EXACT error messages.

That way we won't waste time trying to guess what you mean after the error message has filtered its way through your understanding (or not) of the processes involved.

The log reports the number of rows sent along the link. What happens to them is no concern of DataStage's, except to detect errors. That is, DataStage does NOT report the number of rows affected.

This is the lock table in Progress, not the lock table in DataStage. You can discern this by the square-bracketed entries in the message; [ODBC] is the ODBC driver manager and [ProgressServ] is the Progress database server. You need to find out why that lock table filled. DELETE is, of course, a tra...

Updates are never rejected. You can issue a statement against the database such as UPDATE table SET col1=value1,col2=value2 WHERE 1=0 and, although no rows will be affected, none is rejected in any sense. DataStage plays by the same rules.

Try the dssh command instead of the uv command. They are not identical, but may give us some idea what is happening.