DSXchange

Ask your DBA. If the DBA has only configured a maximum of 20 listeners (connections), then you won't be able to use more than that number. Within that limit, it depends on what you're loading the database server with - are you issuing 20 variants of "the query from hell"? Others have noted that the ...

You can create a small Windows application to dump the worksheet in CSV format (and, perhaps, to initiate a file transfer), and invoke that remotely from the UNIX machine. Otherwise, you need to acquire a UNIX-based ODBC driver for Excel.

There are very few DS_... tables (the actual number depends on what edition of DataStage you have installed, but it's fewer than ten in most sites, not counting the per-job DS_TEMP tables). The information you require is in DS_JOBS and DS_JOBOBJECTS. Search the forum, or download Kim Duke's utilitie...

My reqirement is to do everything in one job. Why? Sometimes (often) a more modular approach is far easier to maintain. Take some advice from an experienced developer - this (everything in one job) should never be a requirement. If "they" try to impose it, challenge them to provide a good reason. I...

Provided you only want inner or left outer joins, then you can use the conventional lookup mechanism in DataStage, using a Transformer stage. The stream link can come from one data source, the reference input link from the other. Obviously you need to generate a suitable reference key expression, on...

Etiquette Note
We do not do "urgent" here. This is an all-volunteer site; no poster gets paid for posting. If you want "urgent" sign up with your support provider for premium service, and learn the true cost of urgent.

Lack of planning on their part does not constitute an emergency on ours.

Create sufficient columns to handle the maximum possible number of product code and product versions. Based on the size of the input columns, this won't be too many, perhaps 10. Split the incoming pipe-delimited fields into separate columns, perhaps using a Field() function. Then run this wide colum...

There is an argument never to use any of these, but to maintain control and propagate warnings up to the master control job sequence and handle them there. You can build in enough logic to ensure that the typical abort situations do not even occur.

Make sure also that you partition your data such that any one customer's data can appear only on one processing node.

I am uncertain about how to do ranking in DataStage, as I normally rely upon the database RANK function to perform this task.

DataStage clients connect via a proprietary protocol called DS Objects. The dsprc daemon listens on port number 31538 (or, if you are running a version earlier than 6.0, on 31438). Disabling telnet (port 23) will not affect the operation of DataStage. If you still want to telnet to the DataStage ser...

Yes it's an old post. However, wearing another hat, I have just re-worked this document which may assist anyone wanting to create I-descriptors (or other UniVerse file dictionary items) in the future. There's probably too much there for DataStage, but too much is probably better than not enough.

How do you know the document has not been created? How are you attempting to create it, and where? Are you using a default style sheet, one created by importing metadata, or a custom style sheet? What stage type(s) are you using? Some XML documents (such as during compilation of a job sequence, or r...

Probably not all users having read permission to the hidden files such as developer.adm and/or operator.adm on the server.

You might find this post illuminating.

Conversion to HTML has disrupted some of the graphics slightly - this is not my fault!

This presentation is taken from one of my training classes, so the answer to your next question is "only in exchange for money".

Yes.

Or, more precisely, no.

A sequencer is that component in a job sequence that makes an "any or all inputs have fired" decision in a job sequence.

The term you needed in your question was "job sequence", not "sequencer".