DSXchange

... and documenting them clearly, concisely and grammatically (in short, professionally) to ease the learning curve for those following, particularly in the case of those "deviations" mentioned earlier and in other cases where the "law of least astonishment" needs to apply. The ability to create a s...

OK, so put the control record //PURGE.SETTING into the job log.

So you have severely castigated the provider of the data? Such feedback is vital in improving data quality.

It's one of those that, if you want to use it you have to add it. On that basis you can conclude that its default value is $UNSET.

You could just set NLS_LANG to an appropriate value. (This is the environment variable used by Oracle, for example.)

Or you could try using the NONE pseudo-map in DataStage.

File Set or Lookup File Set? They are different beasts. How big is the reference data set (number of rows and estimated/calculated row size)?

What else is the job doing? Any sorting or aggregating?

And stop thinking that row/sec is a meaningful metric of "performance" in ETL. It isn't.

@NULL remains the correct way to generate null. Perhaps your database converts null to "" on loading. Check with your DBA. What stage type are you using to effect the load?

There are myriad conversion functions, such as StringToDate(). Research them and choose an appropriate one.

Welcome aboard. Try what Oracle does under the covers. If InLink.TheNumber = 0 Then 0 Else InLink.TheNumber / Abs(InLink.TheNumber) or, if you prefer, try this. If InLink.TheNumber = 0 Then 0 Else If InLink.TheNumber > 0 Then 1 Else -1 I'm surprised you could not work that out for yourself.

$INCLUDE DSINCLUDE JOBCONTROL.H ErrMsg = "" RoutineName = "MyRoutine" hJob = DSAttachJob(TheJobName, DSJ.ERRNONE) JobName = DSGetJobInfo(hJob, DSJ.JOBNAME) If JobName Matches "'-'1N0N" Then ErrMsg = "Could not attach job." End Else * Optionall...

You just have to look at the abysmal way the GUI was written to answer that. How many other grids have you ever encountered with zero rows and you have to right click to create a row before you can use the grid?

Sheesh

You only need to put non-default ones back.

You don't need to anything. If you want the same settings as project default to be in place, just run the job again - the absence of control records will be understood to mean (a) that you want the log to be purged using default settings and (b) that you want the control records to be created. This ...

You have two dots, I have one. Choose "Link Variables" from the operand menu in the expression editor, choose "Inputs..." from the next menu that is presented, and choose the NOTFOUND link variable for the reference input link from the list that is then presented.