DSXchange

Thank you for detailed solution. So it appears that the job monitor had not been started? (Should've thought of that - first question from support analyst - is it switched on?)

The sort command is slightly different on different platforms. Check man sort to verify what options pertain to your system. For example, a numeric sort may be specified with a -n option rather than suffixing the sort key specification.

It depends to some extent on the start date for your Julian - there is more than one standard. DataStage uses 31 Dec 1967 as day 0; other systems use 31 Dec 1899 or 31 Dec 1969.

There are some transforms/routines in the SDK that will help if you need a different base than DataStage's.

Variables declared to be in COMMON definitely can not be used across jobs. Indeed they are limited to one process , which means that they aren't even shared between the job process and a subordindate Transformer stage process. And, unless the Transformers are directly connected (so that they are exe...

Scroll to the right in the columns grid to find out where to handle incomplete records.

Specify the original read as VarChar(250). When you need the first 100 characters, use substring techniques - there's no need to re-read the file.

Even setting a threshhold of 5 will surely apply separately to each processing node?

Are the columns delimited by some character? If so specify that information when importing the table definition, and use a Sequential File stage.

Otherwise, provided there's a small number of variations, the Complex Flat File stage may be more appropriate.

telnet uses port number 23. dsrpcd listens on port number 31538. This is the port that DataStage clients use. You may have firewall issues, even though you can establish a telnet connection.

Nope. Count() function returns actual count (of occurrences of substring in main string, without overlap), whether zero or larger.

I find myself wondering if a Complex Flat File stage might help here.

But, if the source data are sorted, an approach using stage variables to detect change-or-otherwise in the Y records will definitely work.

Why ask us? You work for PeopleSoft, for goodness' sake! Ask them, and let us know! As far as the DataStage connectivity is concerned, no-one has revealed anything to anyone outside the company, but their track record in keeping up with technology has been fairly good in the past. Let's hope IBM int...

Not with so little information. Can you please post actual error/warning messages? Some idea of your setup would be useful too - for example what might be trying to monitor jobs? MetaStage? Or are you working in a cluster, such that exchanges between player processes on different nodes and between p...

I vaguely remember that providing zero for the identity column also triggers it to use an auto-incremented value. Or is that Red Brick?

Anyway, not inserting into the identity column at all will work, since "next available" is its default value.

You bet. And what are job designs and TX maps if not metadata?

From Designer choose Help (or press F1). Bring up the topic BASIC Tasks (or Alphabetical List of Functions if you prefer). Drill down into Data Formatting. In there you will find more than you wanted to know about Iconv and Oconv. But, if you do want more, there's more in the DataStage BASIC manual,...