DSXchange

Definitely a question I'd be posing to my support provider with a strong recommendation to involve the Advanced Technical Support group who have a better chance of determining the limit, for they have access to documentation that mere mortals - including those in the regular support centres - never ...

In server there's a little more that might happen. There's an ancient and long post by me that explains all the gory detail. You left out: before any rows are processed execute before-stage subroutine if any for each reference input link evaluate the key expression on each Key column and request mat...

(I don't have access to PX right now.) Does the Join stage have a "link execution order" tab?
If not, disconnect all input links from the stage, then re-attach them in the order you now require.
You will probably have to re-defined the join keys and types, having done so.

Have DataStage check the Netezza load log, for example in an after-job subroutine or in a job sequence downstream of the Job activity.

Can you try it naming an input column explicitly rather than using a job parameter reference? I have some doubt as to whether Modify stage can use job parameters in this context.

If that works, insert an upstream Column Generator stage to load the job parameter value into a column.

If you use Entire partitioning on the stream input of a Lookup stage and there is more than one processing node, then - yes - you will get duplicates. If there are N processing nodes you will get N copies of every row.

Post the dsjob command from the script. In particular does it use -jobstatus to wait for the job to finish?

Does the script subsequently use the -jobinfo option to determine what happened?

Ask yourself this question instead - would it make any sense for the Aggregator stage to use runtime column propagation?

Assuming that only one of these will occur in any one row, change the derivation of sv0 to sv0 --> Index(InLink.TheString, "C/O", 1) + Index(InLink.TheString, "DBA", 1) + Index(InLink.TheString, "T/A", 1) et cetera as required. The Index() functi...

These appear to be "number of days since an arbitrary zero" type Julian dates. Once you work out what that "day zero" is, you can map that date onto DataStage's Julian date and be able to use the offset to convert your dates.

I haven't played with version 8 yet but, in ODBC.H (in version 7.x and earlier) only the twelve data types that are supported are enumerated. Provision is made for Binary, VarBinary and LongVarBinary, but they are disabled in 7.5.1A (which I'm working with this week). Further it's an Oracle shop, so...

I'd also advocate a Transformer stage, with a stage variable that "remembers" which section you're currently in and which is used in the constraint expressions on the output link. The stage variable is updated only when a section header row is processed.

The sun was shining on the sea, Shining with all his might: He did his very best to make The billows smooth and bright-- And this was odd, because it was The middle of the night. The moon was shining sulkily, Because she thought the sun Had got no business to be there After the day was done-- "It's ...

The sun was shining on the sea, Shining with all his might: He did his very best to make The billows smooth and bright-- And this was odd, because it was The middle of the night. The moon was shining sulkily, Because she thought the sun Had got no business to be there After the day was done-- "It's ...

What kind of "Julian" date is it? There is no universal consensus about what a Julian date is. So what's yours? For example it is the ordinal day number in the current year, or a number of days/seconds/microseconds since some arbitrary zero?