DSXchange

Sorry, just couldn't help myself juxtaposing this against the previous thread in this forum!

Guess so.

Using that SQL, every row you get back will contain the four numbers 1, 2, 3 and 4. Is that what you require?

Nah.

Don't need no stinkin' metadata.

The question was "read", not "parse".

I guess we don't want to guess any more. Let's await the original poster's amplification of what, after all, could be an interview question.

What is the limit on the length of a command in your particular UNIX? Are you reaching this limit?

What WAS your response?

There is a theoretically infinite number of environment variable names, all of which *could* be added to DSParams.

Check whether the hashed files in the repository, particularly DS_JOBS, DS_JOBOBJECTS and DS_ROUTINES, are corrupted.
Use the Administrator client command interface and use UVFIXFILE command on each.

You can't do that in a server job.
(Moved, as requested)

Exactly. You can use a job parameter to supply the value. Your overall strategy may need to jobs - one to generate the value and the other to select rows from Oracle - controlled from a sequence which would also manage passing of the value.

Re-read my response. DataStage is alerting you to the fact that some integers have more than three digits, so you may end up losing data.

The settings in DSParams are only for version 8.0 and later.

Try running the job using the command line interface dsjob with the -jobstatus option. Let us know what is reported.

And be rigorous in your correct partitioning - and, perhaps, sorting - of data.

"LRG____" is not a SmallInt, which is why this row is rejected.