DSXchange

No. There is (currently) no scope for user-defined generator routines in the Row or Column Generator stages. You could build your own (Build) stage, or you could invoke your own routine from a Transformer stage. That exhausts the possibilities in the current version. If you would like to see this ca...

There's a Cancel button, but it's non-functional after a query is submitted.

The ability to cancel a query request submitted through the data browser would be extremely useful.

Welcome aboard. Check that no-one else has the job open in Designer or Director. If they have, get them to close it. Open up the Information Server web console to the Session Management page and identify the session whose Session ID was given in the message. You can disconnect this session (at the r...

All DataStage processes read dsenv to set up their environment. You can override by definining ODBCINI as a project environment variable and, possibly as well, bringing that environment variable into selected jobs as a job parameter. Use $ENV as the default value, and override as needed.

There is only DATETIME. It should accept regular date formats without a time component (try that). If not, supply 00:00:00 as the time component.

So does APT_CombinedOperatorController in the error message. I was trying to make a point.

Several. One is to purchase MetaStage, which allows you to capture process metadata automatically. Another is to write routines using the DataStage API, whether in the DataStage BASIC language or in the C language. The DataStage C-callable API is documented in the Server Job Developer's Guide and in...

Is this a server job (as marked) or a parallel job (as posted)? The answer will be different.

Very well. It's a binary number, representing the interval between some arbitrary (but constant) zero and the date/time in question.

There is NO FORMAT in the sense of years, months, days, hours, minutes, seconds.

This article might be what you are seeking. You get a preview of a DVD that you can purchase. Details are at the site.

Terminal type widths supported are only 80 and 132 (and, perhaps, 400). 1000 would be ignored and the previous setting used. You probably need an approach that does not use "terminal" output but, instead, directs output to a file. SETPTR 4,1000,20000,0,0,3,BANNER MyOutput,BRIEF SELECT * FROM HashOth...

What are your criteria? "Better" is such a subjective term.

You definitely can.

Get rid of the metadata mismatch (the Scale figure for Field1) then see if View Data is effective.

Is it always three source lines per output line? If so, all you need is a Transformer stage.