DSXchange

0 NAME VARCHAR(20) NOT NULL PRIMARY KEY 1 READONLY VARCHAR(8) 2 OLETYPE VARCHAR(20) 3 CATEGORY VARCHAR(60) 4 DESC VARCHAR(60) 5 JOBNO VARCHAR(5) 6 JOBTYPEIND VARCHAR(5) 7 JOBID VARCHAR(20) Size limits on VARCHAR data types are not enfo...

Generate integers 1 through 8000 and divide by 100 downstream. The problem probably is related to internal storage of floating point numbers but I am unable (and, indeed, unwilling) to devote time to investigating more closely. As well, I'd probably need source code for the generator operator, which...

You can - expensively in terms of transferring data between nodes - limit your BASIC Transformer stage to run on the conductor node using a node pool. Otherwise the parallel routine could operate "right to left" using Mod() function to identify each thousands component and build a string containing ...

You are including the parentheses with no space between the name and the left parenthesis? A space might cause the compiler (parser) to identify the function name as a variable.

Ensure that all columns in the Join stage are marked Nullable.

The problem may be in the "and so on" piece or in the order of execution of your stage variables or in the output link constraint expression.

Can you please post exactly how you have derived ALL your stage variables, this time enclosed in Code tags so it's clearer what you've done?

Do not attempt to obtain the status of the master job from its own job control "window". If you do that the status will always be "running". You could certainly do it from the job control code of a separate job, executed after the master job finishes, or you could do it in an after-job subroutine in...

There's more to DS_JOBS than is apparent from the file dictionary. And there is a relationship with DS_JOBOBJECTS to preserve. That's why we need to know exactly what you did - the actual commands used.

No, it's the other way around, a 7.5x2 client talking to a 7.5.1A server. I have not had the opportunity to try with a 7.5.1A client talking to a 7.5.1A server but suspect that the same bug would be seen there also. Currently I am using 7.5.2 and the symptom does not occur.

ROOT is a reserved name, and can not be used as a job name. This is undocumented, but even the visible portions of DS_JOBOBJECTS make it clear why it is so. You would need the same name for the job record and for its root (entrypoint) record. Duplicate primary keys are forbidden.

Are you meant to add (for example what if one date had 1 in more than one row for the same column)? If not, what is the rule for combination? The approach, nonetheless, is to build the rows in a Transformer stage, outputting only when processing the last record in each group (date). You can identify...

Actually using .\NUL as source is a Bad Idea - it will deliver an infinite amount of empty lines. This is a useful technique in scripting, but outside the current discussion. You can use a Transformer stage with a stage variable and a constraint of @INROWNUM = 1 to generate a single row. The Transfo...

Experiment with VarChar and LongVarChar data types rather than Text.

Send money for free receipt.

The Web Services PACK is separately licensed.

Apart from "don't break it in the first place," you mean? This is going to be tricky. Most of the issues arise because DS_JOBS is no longer synchronized with DS_JOBOBJECTS. Can you try moving the jobs back whence they came, and see if they're OK again there? There are many internal references to job...