DSXchange

It keeps the original generated SQL anyway. Just to keep it happy, preserve your user-defined SQL, switch back to generated SQL, fill in one or more table names, then switch back to user-defined SQL, reinstating your SQL if necessary. That should make it happy.

Look in the job log for Oracle warnings.

It's hashed file, not hash file.

Preprocess with a before-job subroutine. This can write a new file, without header or footer, as well as reconciling the row count and preventing job execution where the counts fail to reconcile.

You're not able to employ a BASIC Transformer stage?

Is port #50 blocked by any firewall software?
Port #50 is usually reserved for remote mail checking protocol; it seems odd that this would be needed by an installation script.

Hope wrote:I did that in before job subroutine but I have space issues. When I unzip the files I get the error " No disk space".

Disk is cheap.
Get more disk.

Yes, basically the metadata in your job must match the metadata reported by the database server.

Take a class. TX is totally different.

Like putting your right elbow in your left ear some things are impossible. You need to pre-process the zipped files with a script that unzips them, then you can use a File Pattern in the Sequential File stage to process the unzipped files. Or you could create a loop in a job sequence that unzips one...

Not "different box", only "different platform". If both boxes are AIX, for example, all should be well. If DB2 is on AS/400 or mainframe you have to use the DB2 API stage (and therefore can't use DB2 partitioning).

The latter two are just warnings - alerts, if you prefer.
The first is coming from a composite operator - you need to prevent operator combination to determine which stage is actually generating it.

I would have expected to see CURR_CODE = 'ABC', for example, not CURR_CODE = ABC.

Essentially you need to format the date precisely how Oracle's date picture is set up, or explicitly to specify TO_DATE with an alternate date picture.

TERM
SET.TERM.TYPE
SETPTR

The connection between your client machine and the DataStage server is broken. Check the usual things (network cable unplugged, network card inoperative, etc.)

It can not be changed. Ans is short for "answer". You must assign the return value to this particular variable.