DSXchange

Read with Sequential File stage as single Varchar field. Perform all parsing and conversion in downstream Transformer stage.

Man with 1934 Welsh halfpenny wishes to exchange for one exactly the same.

DataStage BASIC can help here. The STATUS statement returns, among other things, the size of the file in bytes. Use in before-job subroutine.

You need an additional filter to check the entire DS_JOBOBJECTS record for the (possibly partial) name of the table, maybe constraining that to records for which OLETYPE ends in "put". Use EVAL and @RECORD in the query - search DSXchange for examples.

It's not entirely an NLS issue, it also relates to the way that the different OCI versions report metadata.

You could use a before-job subroutine to test for non-existence and zero length. Setting ErrorCode to a non-zero value will abort the job.

Nowadays (since version 8.0) DataStage uses the Information Server scheduling service.

Try putting a space between "Step" and "-1".

You can't "fix" it. The OCI reports multiple bytes per character when metadata queries are executed.

That is, you don't put a "%" in front of the 6. Why not take the leftmost 19 characters of the string and convert that (actually it will already be in the correct format for standard timestamp)?

Hashed files store data according to a hashing algorithm. Any previous sorting will be discarded.

You could use a stage variable for each Oth column testing whether the value is less than Prim and higher than anything already encountered. But a routine would, in my opinion, be easier to maintain.

The space character in the directory name is your problem. As noted, you can enclose the pathname, or the directory name, in quotes.

Have you misconfigured the connection? That "server name" looks like a port number to me.

What did you expect to get?