DSXchange

Simple logic tells you that you need two passes through the data. You can not know (sum of all costs) without one pass through the data. Load these totals into a hashed file keyed by whatever it is you're grouping (categorising) by, then calculate the percentages in a second pass. Or you could load ...

Presumably you have a time dimension table in your DW. You can roll forward until the desired attribute (as retrieved from that table) changes value.

You need to be totally sure that any initial value that you assign to a stage variable will never, ever appear in data. Including @INROWNUM <> 1 is a mechanism that I call "idiot proofing".

The default in a Sequential File stage is to report a zero-length string ("")as NULL. You can override this behaviour in the properties. Null field value property in parallel, NULL value property in server.

I recently rediscovered a post about MFILES and the rotating file pool, written by Dave Meeks (now at Ascential Engineering) in 2002 on a forum for UniVerse. I reproduce that post here because it's useful information. For UV read DataStage; the arguments still hold. >We recently had a situation wher...

Yes and no. Chapter 2 of the Parallel Job Developer's Guide will aid your understanding, even though you're using server jobs. It's about process boundaries. 1. A passive stage between two active stages is a process boundary. 2. An IPC stage is, ipso facto, a process boundary. 3. The invisible passi...

There is no Join stage in server jobs. From your description I believe you have a constraint expression in your Transformer stage that is only allowing rows to be output where the lookup succeeded. Another possibility is that you are delivering NULL to a column that is defined as NOT NULL in the tar...

Welcome aboard! :D DataStage is entirely driven by the metadata. Therefore, unless your tables are similarly - preferably identically - defined, there's no much option in DataStage than to create many different jobs. Create a template from a job that moves a generic table, and optionally make its na...

Then I can only surmise that there's something awry with the ds_ipcopen() space checking algorithm. Have you had any feedback from your support provider?

As Siva suggested, forward compatibility is not a problem. The process of updating without uninstalling automatically updates all objects in all projects. (You don't get a choice on this.) However, you can't go back, so make sure you've got a verified backup, and an export of the project, and an ext...

You can use a pair of stage variables, and rely on the fact that stage variables are processed in the order in which they are defined in their grid. Techniques have been posted before, search them out. Quick example: svIsChanged If (InLink.ColName<> svPrevValue) Then 1 Else 0 svPrevValue InL...

There's nothing I know of to prevent this problem from occurring.

It seems to be minimal if you don't have any other Windows applications open when using DataStage clients. But this is not always possible.

Search the Forum for column definitions for RT_LOG, for example here

OLE (object linking and embedding) is a Microsoft Windows technology. DataStage clients make use of OLE; they use objects exposed by dsobjects.dll (this has different names on earlier releases), which is usually the "OLE server" in question. Basically this message means that something has occurred i...

While you can have multiple projects on the same machine, it's always a compromise to do so, which is why separate machines are to be performed. For example, in development it's possible to get into situations where the machine (or the DataStage Engine) needs to be re-started. Having production on t...