DSXchange

Hi Rajesh, Check the metadata of the Dataset in each job. It is complaining about the number of columns found in each column to get appended. No it isn't. "Segments" means physical data files. You can see the segments for each node (when that node is selected) in the bottom pane of the Data Set Man...

I think it's the other way around - the last line in the file lacks a line terminator. Because the metadata specifies that each line has one, the warning is thrown on the final line.

If you are writing routines in DataStage BASIC why did you post in the parallel forum?

And the answer, as always, is "it depends". What kind of operator? Is the stage constrained to executed in a node pool? When's the interview?

DataStage itself does that within the Repository, though it uses its own idiosyncratic standards (the "UniVerse" database standards) for storage of "collections" and, where necessary, collections of collections and so on. Moving these objects should be no big deal, so "E" and "L" are taken care of. ...

As you are importing the table definition for this particular sequential file, you will find that double-quoted CSV format (which is what you have) is the default, so all you need to do is to specify whether or not the first line is column headings. The table definition will then be sitting in your ...

Search will be your friend. It has been explained previously.

When is the interview?

How strange!

I just did a search (exact match) for "Invalid character conversion found converting to ISO-8859-1, substituting" and got 12 matches.

Separate commands.

Checking temp space "later" is of no value. You have to check it "during".

As suggested, a Nested Condition prior to the Start Loop activity is an efficient technique. Don't even enter the Start Loop activity unless the length of the list is non-zero.

satya99 wrote:Is there any command in unix where we can see this export process.

No.

Then why is it complaining of Parameter 4 (',"@FM","A")') ?

Silly thing is, the source code is saved as a single string, so there's no sensible way it can lose a line or two. (The insensible way, of course, is bad coding of the client/server interface, but we don't have access to the source code for that. It would be sensible to report this through your supp...

The point about sharing with the DS parallel ancestor is not correct. DS parallel ancestor was called Orchestrate (still is, but now it's part of DS) from a company called Torrent Systems. It had an earlier name, but was primarily about automatically scalable parallel execution (of anything, not jus...