DSXchange

Use a Transformer stage output link constraint to enforce your business rule. Good rows are pushed out that output link; all other rows (the rejects) can be pushed out a second output link by making the second output list a "rejects" link.

You will need to write this yourself. Use a Routine that stores the current value in a variable declared to be in COMMON.

How many rows? Rows/sec is an almost meaningless metric for a whole lot of reasons. For example, the start-up time and close-down time are counted in the elapsed time, even though no rows are processed. For a small number of rows, you might also be waiting for the (IPC) buffers to fill.

(a) There isn't one, but one is promised for the next ("Hawk") release.
(b) No.

Seq A can include a Routine activity that loops until the job in Seq B has finished. FUNCTION AwaitFinish(JobName) * Waits for named job to finish $IFNDEF JOBCONTROL.H $INCLUDE DSINCLUDE JOBCONTROL.H $ENDIF EQUATE INTERVAL TO 10 ; * seconds between tests EQUATE RoutineName To "AwaitFini...

Supply only the key column(s) on the link that looks after DELETE operations. Use user-defined SQL of the form

Is there some regularity to the names? Do you want to reset them all to the same value? If yes, then it's standard SQL.

The transaction size is already "all rows"!

You can demonstrate that the problem is not in DataStage by changing the job to write its records to a file. This job will fly. Then create a second job that does nothing but read that file and update the rows.

The fact (already stated) that the entire record has been read as a single string, presumably because the file contains more than one record type. Note the name of the field that is being attempted to be extracted.

Training class DX436 "Advanced DataStage Enterprise Edition"

You need to reduce the string so that it can fit into Char(1). Since you're reading the entire line as a single string, the Field() function is returning the quote characters as well as the quoted value. Therefore you also need to Trim() the quote characters from the result of the Field() function.

1) C++

2) A BuildOp becomes a stage that you can use. Stages (and their links) have properties. Since you're designing the stage, you need to specify what properties.

3) Yes, but you must have something there. A reference to a property is the usual alternative.

Use the Permissions tab in Project Properties in Administrator to assign DataStage roles to your group.

Create the dsadm user identity for administering DataStage.

First check the Permissions tab in Administrator. The message suggests that the non-dsadm user is not in any group to which the Developer role is assigned. I think the other messages are spurious; the fact that you can log in via the Administrator client suggests that DataStage is set up OK; do you ...

The warning can safely be ignored. It informs you that a point has been reached where the hashed file will not fit in the write cache, and that therefore the hashed file writes will go to disk. Disabling use of the write cache will slow things, of course, but will prevent the warning. The write cach...