DSXchange

chulett wrote:Well, that's certainly intuitive.

That's why they're called BAT files.

Use Director. The current run is black, the previous run dark blue, earlier runs light blue.

You can print from Log view, which includes a Save to File option.

Another possibility, depending on precisely what you want to do, is to run Job2 from Job1 using the UtilityRunJob() function.

Your network administrator is the most likely to be able to help. The problem is "general network error" - we can at best guess. Your network administrator can diagnose.

What does Word Investigation tell you this string generates as a pattern? Add a pattern override to discard the "(sp?)" piece.

The string "(sp?)" conventionally means "spelling doubtful".

The drivers are supplied with DataStage/QualityStage. Use the wire protocol driver for preference. Configure ODBC by editing $ODBCINI (usually the .odbc.ini file in your DataStage Engine directory) and adding the DSN to the uvodbc.config file in your project.

Grouping by 12 columns? That is very highly likely to generate a complete set of unique records. Do your 216 records have any duplicates based on these 12 fields?

Not using server jobs. Only the ODBC and UniVerse stages support mutiple returns on reference inputs.

However, if you effect the join within Oracle, the result of the join will contain all matches, and these can be fed into your DataStage job through a single OCI stage.

No warnings are logged if your Lookup stage specifies "allow duplicates".

Hash partition by the lookup key on the stream input and either Hash or Entire partition by the lookup key on the reference input. Do check to see whether there are duplicates in your reference input - if you don't want them interpolate a Remove Duplicates stage on this link, or simply include a DIS...

Only since you edited it. It was identical!!!

A set of date handling routines can be downloaded from here

"Step" is Orchestrate terminology for what DataStage calls a "job".

You need to track down the cause of the SIGINT signal that caused the job to abort. As Arnd suggests, look for other entries in the job log, also perhaps in the RTI Agent log.

U is one of our members. U is unlikely to want to do what you suggest, since it was not U who posted the question. The second person personal pronoun in English is spelled "you".

ArndW wrote:I am not sure what "V LOOKUP" means, but generally lookups are case sensitive.

In parallel jobs you can choose whether lookups are case sensitive or not. At least in version 8.x.

Moderator: please move to server forum (based on posted job type)