DSXchange

Output mode needs to be 'Use trigger column' if you want a change in value of that field to drive filename changes in the output.

Here's one approach - an example of a custom routine that takes in the three values you would need to call the function. This can be used in a Routine Activity stage and the output from this can drive a downstream decision: $IFNDEF JOBCONTROL.H $INCLUDE DSINCLUDE JOBCONTROL.H $ENDIF rJobHandle = DSA...

That would work... as long as you explicitly posted a warning to the job's log when the lookup succeeded.

Another method would be to check the link row counts post job via DSGetLinkInfo (which is how I've done it in the past) and make your decision based on that.

I have three rather complex SOA / RTI enabled jobs that I've inherited. They implement just the functionality that the design specs called for - all basically take XML input and perform a complex series of database changes. My question is around a new bit of functionality being requested. "They" wou...

There's no mechanism for this in job sequences, unless you can come up with a regular expression or command (script?) that turns the file into a delimited string. Correct - but when you do come up with that something, the mechanism is the UserVariables stage in conjunction with the Start/End Loop s...

Now, I need to look up that process date against the target table and then decide if I need to run the job or not. So, one way is to split the above job into two where I read only the first row in a seperate job and then lookup against the process dates in the target table. After that, based upon t...

That's it!

I've not had to do it, not having run into cwazy peoples who create case sensitive object names in Oracle, or ones with spaces in them, but when you do you need to wrap them in double-quotes.

Use quotes around any reserved words:

"YEAR" POSITION(21:24) INTEGER NULLIF "YEAR" = X'00000080',

Don't recall if it wants single or double quotes, but one of the two should fix your problem.

Was wondering about that after I posted it... never had the 'pleasure' of working on a Windows based server.

Cool... we were rapidly getting to a place where I would have no idea what to suggest next, except perhaps to see the job itself.

Yes.

Please start a new thread rather than (further) hi-jacking this one.

I meant each record as one single field in the stage, which it sounds like you are doing.

Turn off the quotes.

Use can use User Variables in the Loop Definition 'Delimited Values' prompt.

On the output Sequential File stage? Interesting. What about quotes? Are you writing this as one long Varchar field without quotes - i.e. set to '000'?