DSXchange

No, simply because there's nothing that allows you to sort a row.

I assume you want a result something like

Link Collector stage, Transformer stage, Aggregator stage ("Last")

8.x must be a standard installation.

Two 8.x servers on the same machine are not supported.

The combination of 8.x and 7.x is supported, but the 7.x must be the -itag installation.

You don't need to change anything in the operating system.

You DO need to get the job that populates the hashed file working properly. It's THERE that the mapping must be set properly. What is the source for this job (file or table)?

Has your UNIX administrator enabled large file support, or is the UNIX file size limit 2GB? Also, please check the ulimit settings for the user that actually executes the job.

Ask for more specifics. WHAT warning? Were row counts reported? What technique was used to attempt to see the data?

Following is the code i am using... If IsNull(DSLink3.FIRSTNAME) Then ',' Else Trim(DSLink3.FIRSTNAME) : ',' : If IsNull(DSLink3.LASTNAME) Then ',' Else Trim(DSLink3.LASTNAME) And i am not getting any warrning or error.Job is completing successfully. I am handling null also. Only two columns are me...

The file system on which /tmp is mounted filled.

Land your score someplace else.

If you can't find the file and can't view the data, what precisely do you mean by "finished successfully"? What are the row counts reported by the client tools?

Welcome aboard. It's certainly possible in version 8.0.1, where there is a separate stage type for Federation Server (though I suspect, from its properties, that it uses an ODBC driver, or at least ODBC protocols, under the covers). I am not currently in a position to verify or otherwise whether thi...

Does the job that populates the hashed file display Japanese characters correctly when you use View Data on the Hashed File stage?

sanjay wrote:you have implement memory window option in HP unix to resolve above issue below issue .

Please explain how you believe the memory window option solves lack of physical disk space.

I'm not really certain what you mean by "above issue below issue" either.

That has verified that your configuration file is syntactically (and semantically) correct, which needed to be eliminated first.

Now read the next part of the error message, about not having rsh set up properly or $APT_ORCHHOME not visible on all nodes.

whenever you are reading from file or writing to file you need to user the two environemnt variables called APT_GRID_SEQFILE_HOST and APT_GRID_SEQFILE_HOST2 which runs on conductor node, so use APT_GRID_SEQFILE_HOST2 on the file name before the file path name. That's only true if executing in a gri...

You need to set up trusted communication for rsh.