DSXchange

The answer is no.

Project level overrides shell.
Job level overrides project level.

Specify None as the record terminator.

Search DSXchange for "mutex".

The master sequence always waits for a sub-sequence. You can take the sub-sequence code and turn it into a routine that returns immediately (remove the call to DSWaitForJob), but you would then need somehow to code for waiting for all the sub-sequences to finish.

If you can put programmable authentication module (PAM) in place and use shared authentication, then you won't need DataStage credentials. Other than that I don't believe there's any solution. You will just have to keep dsadm (and, I would advise, dsuser) as "service accounts" with non-exp...

It depends purely on the data type that you choose to implement the surrogate key. Theoretically if you choose uint64 then the maximum value is 2^64 - 1, or 18,446,744,073,709,551,615.

Welcome aboard. What do you mean by "better"? What are you trying to achieve?

"For some reason" means that's how you - or whoever did the install - configured it. Or failed to. X:\tmp is the default location for the TMPDIR environment variable (where X is the install drive). When installing on Windows one of the things on your checklist should always be to set up th...

Are you using version 8.5 or an earlier version? The ability to compare pair-wise match weights was only introduced in version 8.5. If you ARE running version 8.5, simply select two adjacent rows (from the same set) in match designer and effect the comparison from the right click menu. Critical vari...

The Join stage will not produce correct results, or may run out of memory, if the data are not sorted. If you prevent insertion of a tsort operator (without providing your own sorting on the input links), your job is likely to abort.

That's because you don't understand the function. MatchField(InLink.TheString, "0X'SDN'0X", 2) will only ever return 'SDN'. What you probably want is If Index(InLink.TheString, 'SDN', 1) > = Then "Y" Else @NULL which would be more efficient than If MatchField(InLink.TheString, &q...

I missed that the VOC entry lacks field #2. Fix it as follows.

Use sub-sequences each with its own WaitForFile activity and Job activity.

What are you blocking on? Initials do not contribute much information to the decision, so the mismatch on middle initial will not penalize the aggregate weight by too much. Select the records in pairs in the match designer, right click and note which fields are contributing which weights to the over...

Provided that the environments are set up compatibly (for example all node pool names available), you should have no issues at all going from 8.1 to 8.5.