DSXchange

Increase the size of your inter-process row buffers.

What you need is the IsValid() function. This is a general purpose validation function for any data type (you provide the data type and, possibly, format picture to the function).

Be consistent throughout with the Unicode extended property.

Does your source string date contain any delimiters? Your use of VarChar(10) as a data type suggests that it does. If so, your date format picture must allow for these.

Irrelevant question. User-defined SQL is passed through to the database server. No, the problem is a metadata mismatch. Please post the record schema for this particular link. You can get it from the generated OSH.

Please post the record schema from the input link and from the output link. You can most easily get these from the generated OSH.

... which is what I suggested you do. I suggest further that PostGres (or at least the ODBC driver for PostGres) does not support partitioned reads.

Writes to hashed files are destructive overwrites. That is, if the same key occurs more than once, the last one in wins.

Every job's status is stored in a separate table. How do you feel about a UNION containing 1000 separate SELECT statements?

The number and type of columns (fields) in your table definition (record schema) must precisely match the number and type of columns in the columns list in the INSERT statement.

No. You have to make the structures the same. Column Generator stages are good for this.

Think through what you've designed. You've probably created a design that doesn't emit the last row. Test your algorithms on paper. Possibly the easiest approach is to add a dummy last row to your source data.

Not in a job sequence. But you can do it in Job Control routine. You might even use a job sequence to prototype the routine, then copy/paste into the Job Control tab of a server job and add calls to DSSetJobLimit() function.

Just dont tell the cops!

If you mean "hashed" file, the storage object available in DataStage server jobs, you have options in the Hashed File stage about where to store. The choices are "in a project (account)" or "in a directory (which must exist)".