DSXchange

No, the agents can be left running if all you need to shut down is the engine (which is true in this case).

I second that, particularly since the site I'm at will be doing exactly what's described next week (or the week after).
:D

Ah, "performance". Is it time for that argument again? For small volumes of data a server job can be started, run and finished before a parallel job has completed its startup phase. This startup phase is allegedly improved (quicker) in version 8.5 but I've not yet had a chance to verify th...

Depends what you mean by "hit". I assume you mean "match". In that case, the match percentage is a measure of hit rate. But some of the clericals may end up being true matches once reviewed (you won't know till that's been done). "Match" in this context is the percentag...

Why are you confused? Server jobs use server stages, parallel jobs use parallel stages, sequence jobs use sequence stages. You even get a different Palette depending on what job type you have open. (You can use server Shared Containers in parallel jobs under certain circumstances, but not server sta...

Whichever one is right for the data type of the join key.

This is an interview question, isn't it?

Search DSXchange for examples - it has been well explained in the past.

Looks like it's reporting the date/time that dsjob was run. This is a bug, if reproducible, and should be reported to your official support provider.

We're getting there.

Your subject is "converting" the routine code. To what do you need to convert it?

There are two Sort stages, even though they're called the same thing. (What else would you call it?) Open the properties in the Stage Types branch of the Repository to note significant differences.

The match specification designer allows you to place passes into a "holding area" so that particular combinations of match passes may be tested. Testing is done within that designer; you don't need formally to run the job. And you can specify a sample of data if you wish.

Stage variables or upstream Sort stage for detecting key change. Other stage variables for maintaining page number for output. Note that you cannot look ahead, only back. But you could sort your data in reverse order!

Put Eff_Date fourth in the list of sort keys.

Of course it's possible.

But it's wrong.

Would you (or your interviewer) use a hammer to tighten a screw? It's possible, but it's the wrong tool for the job.

Use one Aggregator. Process 30 columns (plus grouping columns, if any) in it.