DSXchange

A Lookup File Set includes an internal index on the key columns.

A Sequential File stage would need to be completely imported into a virtual Data Set, but this lacks an index, so that lookups would still require a partial or full scan.

Does that make it doubly urgent?

In that case, I'll double my normal penalty delay in responding to urgent post. We don't do "urgent" here, as has been explained often.

What data types are source and target columns? Without this, we can only guess at the right answer.

Start at the Ascential web site and DeveloperNet (where there is also an RTI forum).

Oconv(14560, "MR2") or Fmt(14560, "MR2") will do the job for you.

Don't ignore the Merge stage, which does allow you to capture failed lookups from each reference input separately. It also requires identically sorted and partitioned inputs and, if more than one reference input, de-duplicated reference inputs.

I'm not doing DataStage at all this week - conducting a Red Brick training class, no access to DataStage. RTI_Enabled is definitely do-able, I've forgotten how, but will check when I can. Job version number can be obtained from DS_JOBOBJECTS ROOT record (field #8) for the job. The key to this record...

(I've assumed you meant four digit year, not three!)

Change defaults from Tools > Options menu in Director.

Search for "-itag"

Yes.

You must have DSN, user ID, password, table name and column names (at a minimum) complete before View Data is enabled.

If you are using environment variable job parameters with $PROJDEF or $ENV) it just doesn't happen at all.

I don't recall anyone claiming that Pivot stage was faster than awk.

Please describe the file (rather than what you're attempting to set in DataStage). Is it delimited or fixed width? Are character strings quoted or unquoted? Have you imported its table definition? If so, did you Load from that into both the Format and Columns tabs in your job design?

The development time for the new jobs should be in the order of minutes only. Update the documentation within the job, delete the existing column definitions and load the new ones. Source and target table names are, presumably, job parameters.

It's not easy. DataStage does not have an inherent metadata checking function. You might have some success by making not only the Data Set control file name a job parameter, but also the Schema File property (which assumes that you have created external schema files) but it's not something I've ever...