DSXchange

This is a before/after subroutine. It is executed either before any rows have been processed (in which case the link row count must be zero), or after all rows have been processed. Its position within the processing stream ensures that it will not stop the job. I'm not sure why you want to stop the ...

No, but you can use it in a Routine activity in the job sequence that runs the parallel job.

You can also look in the job log - every "active stage finishing" message carries row counts for links connected to that stage.

Are you getting this message at row 0 or 1, or at a later row? If the former, check that the first line is not column names. If the later, check that row, ensuring that none of the columns contains a line termination character (Char(10)).

It is not in the installation folder. It must be downloaded from the eServices web site. If you search the forum you will find a link to the actual page.

What is your DEFFUN declaration for DSGetLinkMetaData? This is not catalogued with a "DSU." prefix.

I have also seen something like this behaviour. It also occurs in the job monitor, so is probably a problem with how the link row count is being collected when there is a direct link from a Transformer to an Aggregator stage. As noted, the final row counts are correct. It might be an artifact of row...

Why did you bother with a Routine when a stage variable would have done just as well, and would not have introduced COMMON (which has future implications if you ever want to incorporate this server job functionality into a parallel job)? Regarding DSGetLinkMetaData, do you have the correct arguments...

If you can describe the format of the Control-M log file in metadata terms, you can process it with DataStage. If it has a variable record format you still may be able to do so. You will also need to be able to specify its location to the DataStage job.

Normally it installs into C:\Program Files\Ascential\DataStage\Docs (or the Docs folder wherever you installed your DataStage client). If you ordered XML PACK separately, then it will be on the media on which that software was delivered.

Indentation/formatting is achieved by wrapping the relevant text between Code tags. Select the text, then click on the "Code" button above. Set up four stage variables. The first three compare the three fields. They can take advantage of the fact that a NULL causes a Boolean operation to return FALS...

Your source extraction could be user-defined SQL. SELECT A FROM tablename UNION ALL SELECT B FROM tablename; Naturally this requires that columns A and B have compatible data types but, then, so does inserting them into the one column in your target. If they are incompatible, use CAST to guarantee t...

Perhaps one of the hashed files is hitting its 2GB limit. Have you checked their sizes? You may need to create hashed files with 64-bit internal addressing. Unfortunately you can not do this with the GUI. However, you can do it with a CREATE.FILE or a mkdbfile command - depending on where you want t...

Reset the job in Director and report whether any diagnostic information "from previous run..." is logged. Change the target to a Sequential File stage. This will isolate the problem to being in the Transformer stage or your original target stage. Once you've eliminated the Transformer stage as the c...

Has "someone" changed the password for the database and not updated the job sequence parameter value?

What IS the derivation of column xxxx ?

Does it refer to a now non-existent input column? For example, did you delete one column, or change the name of a link?