DSXchange

De-duplicate the inputs. This is a requirement for the Merge stage where there is more than one update input.

Make sure that the master input does not become exhausted while there are still update inputs to be matched (perhaps by re-assessing which is master).

Switch, Filter or Transformer stage to split into separate stream for each record type; Modify, Column Generator or Transformer stage to supply missing columns; Funnel stage to bring them all back together.

I note that you have also removed the surrounding square brackets.

Check that you have permission to write into the D:\QProject\POC\Controls folder and access to all the parent folders in its path. A quick test is to get into a DOS shell (via cmd perhaps), CD to that folder and create a file, using the same user ID. It shouldn't matter, but can you try setting thin...

It's unhelpful not having the exact error message. Chances are that you're trying to do too much with two few stages, or even too few jobs, and perhaps getting locking issues in the database. Staging the intermediate data, perhaps into a file as the previous poster suggested, is one way, but you can...

DataStage is not able to display anything, since it always runs background processes. I assume, therefore, that you want to generate 365 or 366 rows in a server job and have a separate date in each. Your job can be as simple as Transformer ----> SequentialFile Create a stage variable initialized to ...

Still waiting for definition of "perfect answer".

This is unrelated to RT_LOG623 and is unlikely to be corrected by anything in DS.TOOLS.

Search the forum for this particular error message (leave off the particular job number). It has been fully explained in the past. You have a corrupted RT_CONFIG623 hashed file here.

DataStage does not have "current timestamp"; it only has current time and current date. Do you want these to move along as rows are processed (in which case use Date() and Time() functions) or to remain constant for the job run (in which case use @DATE and @TIME system variables)? You then have to c...

Project-based environment variables are stored in a text file called DSParams, which is located in the project directory. You can copy DSParams, or relevant lines from it, into DSParams in the production environment (project directory). If you wanted to script this it should be reasonably straightfo...

Where is the source coming from? Just because you declare a column to be not null in your DataStage job does not enforce non-nullability. For example, if your source is a text file, the Format tab on the Sequential File stage specifies what will be interpreted to be null (by default it is "") and th...

Surely "they" produced the file using some kind of metadata or design. Get "them" to supply the file layout(s) to you. "Binary" is OK if the data are fixed-width columns. For example, an integer will occupy four bytes. You can declare it as Char(4) and use Oconv() to turn it into a string of ASCII d...

If it's a single mapping file, or even just few, for multiple data files (each having the same metadata), you could simply create a table definition, or more than one, manually in the Repository and use these as the metadata for various DataStage jobs to process the data. In this way you could avoid...

If the size of cache is adequate (no hashed file fails to be cached) then increasing the available size of cache will have no impact whatsoever on the "performance" (whatever that means) of hashed files.

You can run parallel jobs (you need version 7.5x2). Obviously with only one CPU you rapidly run out of processing power. Don't contemplate it for a production environment.