DSXchange

"Mutex" stands for "mutually exclusive" and is one mechanism by which semaphores are implemented. A semaphore is a place to wait. When a process waits on a mutex lock (because, for example, the lock is held by another process) it does not sleep but, instead, "spins its wheels" attempting to gain the...

The reason that partitioning must be the same is to guarantee that any duplicates occur on the same processing node. The reason that sorting should occur is so that least memory can be consumed - once the sort key value changes, the stage can be certain that there will be no more matches against thi...

OK you tricked me. You had the text of a paragraph, complete with underscores at the ends of lines, but you called it a script.

I think you'll find that UniVerse/SQL requires dates to be in 2005-11-15 format (ISO 8601 standard).

Ah, introspection. Or is it introrogation?

... then the reject link could feed a stream that accepts the header but rejects the footer, and these streams could then be processed appropriately!

It appears that the compilers on the two systems are incompatible. This may be a different version, through to different compilers. You or a system administrator must investigate.

You claim the problem is in an FTP stage yet you post the code generated from a Transformer stage. Why? Syntax error: Error in "transform" operator: Error in operator arg: In field "Corp": Expected ";", got: ".", line 87 In field "Corp": Expected ";", got: ".", line 246 The error message suggests th...

I think that the multi-instance thing is a red herring, and has coincidentally occurred at a time when the system total load dropped. The ipc errors are usually to do with row buffering. When you're using a BASIC Transformer the data have to be buffered and translated to and from typeless. This uses...

Get in touch with your support provider. There is a recent patch that addresses being able to run STAN in parallel. Nothing I've heard of for MATCH, but some kinds of match wouldn't have a problem - you might just have to be careful with partitioning so that you could be sure that all potential matc...

But first, ask yourself why it's there. Does someone want to prevent you from hacking jobs in a production environment?

The only one I know of is called a brain.

The apparent order (on the design canvas) can not be changed - the tool does not give you the ability to select the attach points between links and stages - rather this is computed by an internal algorithm in the client tool. You can hover the mouse pointer over a link to determine its execution ord...

chulett wrote:Have you tried performing the deletion from the Manager? There are client tools other than the Designer, ya know.

As of version 8.x there is no more Manager client. Its functionality is all moved into the DataStage/QualityStage Designer. Fewer client tools, yay!

You may use any legal command you find in a manual, including in the UniVerse manuals downloadable from IBM's web site. However the metadata (column definitions) for Repository tables is not in the public domain, nor do they have a first normal form structure. So there is also the question of whethe...

You need to use a UniVerse stage, not a UniData stage, to access UniVerse tables. What you've designed is akin to using a DB2 stage to access an Oracle table - it just doesn't work. Technically the DataStage Repository database is not there for you to store your data. In the next release of DataStag...