DSXchange

Uncheck 'Formatted Output'.

Assuming this is a job being run by a Job Activity stage in the Sequence, then it would seem that your assertion that there is no problem with the connection doesn't really seem true. Double-check the actual parameters you've assigned to the job and use the External Parameter Helper under the '...' ...

Is your search target always on its own as in your example? If so, then it seems a simple equality check is all you need. If the 'word' is buried in a larger string, then a function like Index() or Matches() can be used to detect a substring within a string.

Once you find it, then what?

Include it as a job parameter and then include that parameter in the Before Job routine call. Why a routine here? You can run the script directly using ExecSH before job.

What kind of 'database issue'? Can you post what your actual resolution was?

Adding in dynamic dependancies like that is a complete game changer and goes well beyond simply triggering 'a list of jobs at the same time'. It can certainly be done and Ken Bland's KBA Job Control Utility has been doing exactly that for quite a number of years. Rolling your own would be both an in...

Add a 'key change column' to the Sort stage and then examine the values that come from it. You should easily be able to tell what constraint expression to use for each target.

Did you try searching the forums here? An exact search for "has a partitioning method other than entire specified; disabling memory sharing" returned over 20 matches.

... and here we are in Server world now.

Didn't mean it needed to be included in the routine, just that the O/P could look there as a reference for the mnemonics.

Phantom just means 'background' and the numbers will change each run, so no worries (and no useful information) there. Can you post some examples of the actual error contents for us to see?

Don't attach to the current job, use a handle of DSJ.ME instead. And the STATUS values are the standard ones defined in the dsapi.h include file - 0, 1, 2, 3, etc - a.k.a. DSJS.RUNNING, DSJS.RUNOK, etc.

Lots of people have faced this... records are 'dropped' when they don't match the metadata in the stage.

Next time please post your topics in the appropriate forum, this one is for questions specific to QualityStage.

As Ray noted, display formats are only valid when the target data type is string.

ray.wurlod wrote:This is not the same problem and really warranted a new thread.

Done.