DSXchange

The essence of the new functionality in 8.5 is that the WebSphere Application Server and the common metadata repository support clustering with failover.

There's still not a whole lot that can be done to failover running jobs, because of the extensive use that is made of shared memory.

Is DB2 client software correctly installed and configured on your DataStage server? If you are expecting parallel operation, you may also need to configure db2nodes.cfg. More information can be had from the Configuration Guide for DB2 Connectivity, one of the manuals in the standard documentation set.

This is a SQL Server error. Can you please let us know what it means?

Sure, just hard code it as a single-value sequence in a Column Generator stage.

Can you please advise what you think is wrong with the expression I gave?

Have you tried it?

Or the record was the right length to a human, but contained a line terminator character.

Actually, Andy, SunOS 5.10 is Solaris 10. So that is not the issue. The issue is using the correct JRE which might, in turn, end up being a PATH or CLASSPATH issue.

Let's begin with the terminology. It's properly "hashed" file, not "hash" file. To understand the purpose of DATA.30 and OVER.30 you need to understand the internal structure of a hashed file. Records are organized into "groups" (pages, if you like), the size of which i...

Actually just Field(InLink.TheData, ".", 1, 1) would do it. If there is no period this will return the entire string.

Data in a Lookup File Set can not be viewed. At all. Data in a Lookup File Set are stored in indexed blocks in internal format. You can use orchadmin to view the contents of a File Set from the operating system level, and the Data Set Management utility or View Data within Designer.

rumu wrote: no need to do sorting in database level as auto partition will insert by default an order by clause if source is database

Completely incorrect.

Maybe. Unless you manage to start two at the same second. Granularity of job start timestamp is only whole seconds.

Are your failures occurring soon after re-booting the server? The java.exe takes a while to complete loading into memory (look at the size of it using Task Manager!). Leave the system for 10-15 minutes before attempting to log in to DataStage.

A DataStage job can generate many process IDs. For example a ten stage job running on four nodes may generate 45 processes. Which one do you want?