DSXchange

You will probably resolve this yourself when you inspect the job control code generated by compiling the job sequence. "$ReturnValue" is just a place-holder - it's a way for the GUI to flag that what is wanted is a variable whose name is generated at compile time. The rules for DataStage BASIC do no...

From the code it looks like the only variable that could be unassigned is Arg1. Somehow or other the variable used as the argument in the calling routine (that is, the code generated by the Transformer stage, not one of yours) has managed to create a code path that fails to assign - presumably the c...

No.

The usual way is to rely upon indexing in the target database, and to use a user-defined SQL expression such as SELECT MAX(keycolumn) FROM tablename; This always returns one row, which you can pre-load into a hashed file (with a constant as the key value) or other temporary location for subs...

First thought is simply to change @INROWNUM to @OUTROWNUM in your stage variable derivation expression. This is not viable, because @OUTROWNUM is specific to each output link and therefore not available to stage variable derivation expressions (which are evaluated before any output link is processed...

1. Yes. You can telnet to the machine on which the DataStage server is running. If it's Windows, you will already be in the DataStage environment because dstelnet is the listening service (unless you've changed the defaults). If it's UNIX change directory to where the DataStage Engine is installed (...

When you open the constraints window, there is a four column grid into which you can load your constraint expressions (the second column). The third column of this grid contains a check box that allows you to identify this particular link as a reject link. If you do this, when you return to the Tran...

Since you've got version 7, you might also like to investigate the job "templates" (generators - can't remember the exact terminology) supplied with it for handling slowly changing dimensions. They're not perfect, but can save some work.

Don't think that's related to the fix you quoted. DSU.nmz refers to a Routine called nmz. It's in this Routine (in line 2) that the problem is occurring. Find it in the Routines branch of your repository, and identify a variable name being used as an rvalue, but which does not have a value assigned....

If both sources are passive stages, then you can use a Join stage. Otherwise you have to use a Lookup stage. Read about both in the DataStage XE/390 Job Developer's Guide (which is in your DataStage documentation folder installed with your DataStage clients).

SIGSEGV is UNIX talk for "segmentation violation signal", which signals that your application has tried to access a memory address that it does not own. Your "any pointers will help" was therefore very amusing! Memory is accessed through pointers in the underlying code. Is this problem reproducible,...

As a first step, try using more meaningful subject lines in this Forum. This means that when you or others are searching for solutions to the same issue, they can more rapidly found. <rant> People who mark things urgent have a negative effect on me, particularly when I give these things undeserved ...

A reject link does not have a constraint expression. Instead, it handles any row that has not been processed by any earlier-executed output link. For example, if your Transformer stage has four output links, then you would have constraint expressions on the first three (in defined execution order), ...

The obvious thing in this automatically generated code is that no checking has been done to make sure that all the parameter values were set correctly, or even that job PopDailySavingsTran was attached correctly and was in a runnable state. Check the job log for PopDailySavingsTran and tell us wheth...

Can you provide a more exact context? The terms can be equivalent, but in some specific circumstances they can mean different things. For one thing, "scratch space" may been that memory has been allocated, rather than disk, for example for data type conversions.