DSXchange

That's the same as my RSS. Real Simple Syndication.

Do a collection of shorter sleeps. Check for an interrupt mechanism between sleeps. We 'touch' a file of a certain name into a certain directory, and its presence means the job should stop gracefully.

There, fixed my post just for you Tony.

I have no idea. If a previous post mentioned it, set it and let us know.

It simply stops that environment variable from being set, the setting of which is what causes the core dumps to happen. That's all. No adverse effects that I've ever seen in our Server world.

You failed to search the Forums, that's all. I got eight hits on an Exact search for 'could not create operator sync table'. See if any of them help.

As noted, comment out that whole section and then stop/restart DataStage.

You can only check the status if you do all that in a Routine, which can then be used to populate your stage variables if you like.

How could they? It's all converted Premium Content from the switchover.

How exactly are you passing these parameters in? Default values, Sequence job, command line?

This must be something specific to the Enterprise stage, everything I wrote works fine with any DB stage on the Server side - looks like I made a bad assumption that it would work here as well.

You must be new to playing the hashed file game. When a reference lookup fails, all fields in the reference link are set to NULL.

Explain how many keys you built the hashed file with... one or two?

One other thought, include the wrapper quotes in the stage: select * from table where codes IN ('#p_in_clause#') Then pass in your values like so: A690','R456','F1234 Because of the stripping that goes on, I always try to include outer quotes in the stage if at all possible. Another solution...

Oh please, don't encourage him.

... and don't forget to 'Reset' your job after it aborts and post the contents of any 'From previous run...' entries that may show up.

Everything in there is now NRO.