DSXchange

Have you thought about asking Tom?

Rubbish! A parallel job can certainly be used. Put a DB2 stage feeding a reference link to a Lookup stage, and execute the query in the DB2 stage. SELECT 'X', MAX(surrkey) + 1 FROM tablename The trick is to make sure that the reference input to the Lookup stage uses Entire partitioning, so t...

Just to clarify, the expression (containing the Left() function and activity variables) needs to occur in a job sequence, in the grid where you assign values to the job parameters before invoking the job run request. Is this your case?

1. No.
2. You get the ability to run in "Parallel Extender" mode.
3. Assuming you mean the default.apt file and its colleagues, no.

Do you know what an Orchestrate operator is? If not, forget about using the Generic stage. Obtain, from your vendor, a copy of the Orchestrate Operators manual, in which the operators are documented. Study it, and then you will become aware that the Generic stage allows you: to invoke an operator fo...

Change the partition to be explicit rather than (Auto) and/or change the upstream preserve partitioning flag to Clear. If you choose explicit partitioning make sure either that all inputs to the Lookup stage are identically partitioned on the lookup key or that the reference input is Entire partitio...

Why do you ask? Have you tried it?

I was thinking of the fix_zero option in the conversion functions. Search for it in the Parallel Job Developer's Guide

In a server job separate the date and time portions, subtract one day from the day portion, then re-assemble the timestamp. Oconv(Iconv(Field(InLink.TheTimestamp, " ", 1, 1), "DYMD") - 1, "D-YMD[4,2,2]") : " " : Field(InLink.TheTime...

This is a pivot; it can be done with a Pivot stage. Over-configure the number of pivoting columns, then filter out those generated with NULL in the result.

It's a single string that the function produces. Use substring, concatenation, Fmt() and other functions to generate precisely the format you require. You may prefer to use lower-level functions to retrieve precisely the information you require in your report.

1. Always close clients properly.
2. Invest in hardware that means that you NEVER have network dropouts.
3. Never accidentally or deliberately disconnect the network.

Which database? Your source database, your target database, your staging database, your intermediate tables, your lookup tables? Describe what the schema you have in mind should look like.

Have you configured any other Oracle users?

Rule set files are never in the MDB. Only references to the rule set names are used in designs. The rule set files are deployed when a job that refers to them is deployed. The rule set files are installed on the client when the QualityStage Designer is installed. That's why they're not in an export ...