DSXchange

You ought never to edit any of the header files in DSINCLUDE. There is no such function as DSGetStageLinks(), which is why the message about array not dimensioned is being generated; because there is no such function, the compiler assumes that a token immediately followed by a left parenthesis is th...

1146600 / 716 = 1601.4 so 1146600 is NOT a whole multiple of 716. Not only can DataStage not partition this file, it can not read it without encountering at least one incomplete row. You must get your metadata right, or include handling of incomplete rows, or check that you've been provided with a c...

The number of partitions is exactly the number of processing nodes specified in your configuration file (the file specified by the APT_CONFIG_FILE environment variable), unless this is overridden on the Advanced properties to limit execution to a node pool that is a subset of that group of nodes.

It could be a bug, but I suspect you've lost a VOC entry that needs to be there. What it's trying to do is to open a file unit on a file called "&UFD&", which is a pointer to "the current directory". Check that this item - and possibly one called "UFD_" - exists in the VOC file of the projec...

Load FileB and FileC into hashed files keyed by row number. Use @INROWNUM while reading FileA to perform lookups against these hashed files, and generate the output row by combining input columns from all three. Make sure that FileA has at least as many rows as both FileB and FileC. Handle nulls cau...

Use a job sequence. Create a small job to SELECT COUNT(*) FROM TableA into a hashed file with a constant key value (say "TableA_Count"). You can use VOCLIB as the hashed file or create your own, but it should be created within the project or have a VOC pointer. Create one job that truncates TableB a...

Is it the status file or the log that you want to clear? Your subject says status line, but your text suggests log file. You can, of course, set automatic purging for log files (which are actually database tables in the Repository). Choose Job > Clear Log in Director with the job selected, and chang...

You get this error because DataStage attempts to partition fixed width files by dividing the size of the file by the number of partitions (N) to get the subset of rows to process. However, as an exactitude test, DataStage verifies that 1/N of the file represents a whole number of rows, which is the ...

Using Director, reset the aborted job. Then check the log for any message "from previous run..." which may contain additional diagnostic information. What you are looking at in Director is the last updated status, which is not necessarily the current status of a job. Timings include all time needed ...

How, exactly, do you "stop the DataStage job"? Why do you claim that it's "not working", and what do you claim that the "error" is? After you attempt to "stop" the DataStage job, what messages are logged in the DataStage job log? Are you aware that a DataStage job may comprise quite a number of rela...

The more complete solution is to TRIM all string type (Char and VarChar) key values when loading them into the hashed file as well as when performing lookups against them.

Click on the Format button in your original code, so as to show "proper" indenting. You may have omitted an End statement for example. Indeed, each of your ReadU statements lacks an End statement to terminate the block of statements begun by the keyword THEN. Machine formatting will highlight this; ...

Editing the original post to remove the problem description is singularly unhelpful. Can you please reinstate it so that anyone searching for this problem in future can be helped?

If you're on Windows XP, this error can occur if your network card is inactive (at least with version 7.5x2). I discovered this by accident. Once the network card becomes active again, things work!

Try to avoid aborting jobs.

You can still exert total control over the sequence using specific values written to files (as you propose), without the need to abort. Use custom triggers and/or Nested Condition activities to control the flow of execution.