DSXchange

One can but wonder what their system documentation looks like.
No, I'm not kidding. Documentation.

The job number is given in the first line of the warning message - in this case job number 1809, so you look in subdirectory RT_BP1809. Note that it is the BASIC code for the Transformer stage, not the BASIC code for the job, for which Yamini asks. BASIC code for the whole job is not available; serv...

Even just try SELECT @ID, F1 FROM SDKSequences USING DICT VOC; Queries are not affected by row level locks, so you will at least determine that the SDKSequences hashed file exists and is not corrupted. There is no routine called KeyMgtResetValue supplied with DataStage. The only routines for key man...

Does the Data Set Management GUI in Manager offer any clearer error messages?

Depends.

2005-12-21 can be stored as 1972, the result of the arithmetic expression.

It's less likely to happen accidentally in parallel jobs, of course, than in server jobs, due to more stringent enforcement of data types.

There are three things to check when this error occurs. 1. Existence of the parameter name in the controlled job. 2. Spelling of the parameter name in the controlled job. 3. Casing of the parameter name in the controlled job. If all three of those are correct, open the job activity in the job sequen...

There are two fields on the Command tab in an Execute Command activity. In the first (Command) you put simply the rm command itself. In the other (Parameters) you put anything else that needs to appear on the rm command line. This can include references to job parameters, for example -rf #path#/#fil...

Poornagirija wrote:How to view those columns(column name with space)?

It's not possible. This is not a fault in DataStage; it's a limitation of the ODBC driver for Excel.

View Data is simply not available when a filter command is specified. You will need to verify the functionality of your filter command outside of DataStage, possibly by redirecting its output into a file as suggested by Ken.

In particular, learn from your reading that Entire partitioning puts all rows onto all nodes.

That is the main point from Kumar's posting that will aid your understanding.

There are several strategies for this. At least three have been posted during the life of this forum. What did your search of the forum reveal?

We can not give your vendor's email address, since we don't know from whom you purchased DataStage.

There is no generic DataStage email address. You might like to try the "Contact Us" link at the Ascential web site - note that this will be subsumed into IBM fairly soon.

Alternately you can define a separate ODBC data source name (DSN) for each workbook. Each worksheet in the workbook will be presented as a separate system table in that data source. Some restrictions apply, primarily the need for a proper tabular format with column headings. When importing the ODBC ...

Or, if you are going to use this in lots of places, create a re-usable component (a Transform) containing the kind of expression that Roy suggested, though with Transform arguments rather than hard-coded values. Why not call the Transform "NullToValue"? There are already supplied Transforms called N...

Good, thank you for that answer, but you understand why we had to ask it? There are some tweaks needed for Linux, which you will find in the readme file. It's been some time since I installed on Linux (and that was Red Hat) so I can't remember them all. Hopefully someone else can contribute. Have yo...