DSXchange

Sounds like a full outer join to me, then it's up to you to check for nulls to recognize a mismatch. Guessing that would be a 'Complete Set' in Merge stage lingo. Or maybe 'Right and Left only'? One of the two should work.

KBA = Kenneth Bland Associates, the original authors and who's names should be all over it.

Right, you have a constraint that only allows lookup successes to pass - you need to "turn that off".

See if this helps.

ITToolBox. Name and URL both, oddly enough.

Been discussed here quite a lot. You need two triggers, one "OK" and one "Otherwise", to convince the Sequence that you are handling the error and that it doesn't need to do any such thing automatically. Run both to a single Sequencer set to "Any" if you really don't ne...

All you are getting is a text file with a ".pdf" extension, which of course won't work unless you force it to open with something like Notepad or Word. Sounds like you should take a crash course in file extensions and what they do (and do not) control on a Windows system. Typically, one wo...

How are you trying to "output to PDF" now? There's way more to it than simply using an extension of ".pdf" by the way, if that is what you are doing.

Again, unless you override the values, the default warning limit in the Director is 50 while from the Designer it is zero - unlimited. Which could explain part of your issue with the Director but still shouldn't result in a SIGINT as far as I know.

There's nothing about Ray that is "uncontroversial", including his best practices. And some DataStage features require jobs to abort to work.

Every client I've worked with has used them, most either at my behest or with code I've modified and others have propagated. I've made improvements to that code for years so know most of it "like the back of my hand" as one might say.

Gotcha.

The default warning limit is indeed different between Designer and Director (0 v. 50) but there's nothing stopping you from ensuring both run with the same values.

Your problem is the use of the Sequential File stage, change the job to use an External Source stage as noted here in Ernie's blog on the subject.

So, why is this marked as a "workaround" and not "resolved"? Did you implement something else?