DSXchange

You should be able to use ODBC stage to communicate with Netezza.

Welcome aboard. There's rather more to it than that, as a more detailed reading of that manual will reveal. You are correct about CATALOG.FILE.CACHE but, before that, the hashed file itself must be made capable of being a public cached hashed file. Review the manual, then come back if you have furth...

Sparse lookup with LIKE condition in user-defined SQL in the stage providing rows to the reference input link.

"Not running" can mean "not compiled".

samsuf2002 wrote:I am having a strange issue with my main sequence which was running fine before suddenly started ...

What has changed?

Try re-compiling the jobs.

Aggregator stage always uses double as the data type of computed fields. However it has a Decimal Output option that allows you to specify how the numeric result is to be represented as a decimal number (precision, scale). If scale is 0 you effectively have an integer.

Straightforward enough. Do you have the webservices pack? There are specific stage types (they used to be called RTI Input and RTI Output, I can't recall their new names) you put into the stream. Then you expose the DataStage job as a web service, maybe auto-start, maybe always running, maybe multi-...

If they are different machines also check that the ASB Agent is also running correctly.

For example, if the file is in the project directory (which is called &UFD& for reasons that aren't relevant here), UV.VI &UFD& filename

Alternatively you can run a shell and run vi within that shell.

In particular note that there is no such thing as a log file

Weren't we talking about an already existing stage here? Code only on the per-record tab? A definite maybe, though I would be very surprised if that were the case. Typically you open the file, declare things and allocate memory in the "before" tab and close the file, clean up and free memo...

Can you (or your DBA) monitor the Teradata session to establish exactly what SQL is being received from the connector? It may not, for example, be the CASE that is the problem - it may be that some prior quotes are being stripped out of the query.

Well that, at least, is easily remedied.

Premium membership is not expensive, at less than 30c per day, and helps to fund the hosting and bandwidth costs incurred by DSXchange.

Not in a server job.

Multiply the retrieved values by 100. The values are stored with an implied decimal point. You could also use Fmt(), but multiplication is likely to be more efficient.

No space, or a non-space character, between COL3 and FROM ?

How come there is a FROM in an UPDATE anyway?