DSXchange

Welcome. :D So seriously, you couldn't find any of the XML stages in your palette? You have to have a job open in the Designer (other than a Sequence job) to see the appropriate icons for the job type, but unless yours has been customized they all should be there under the Real Time category: XML In...

You've misread both posts, it seems. Not -jobstatus (something completely different) but rather -jobinfo is what you need to use.

I also use Local containers to make jobs less... cluttered. Logical areas can be encapsulated in well named local containers to make the job flow / logic more obvious. If you need to know the gory details of any particular piece, open the container and take a peek.

I assume you mean 'real world'. Any chunk of stages that you could (re)use in more than one job is a candidate. For code, there's routines, for stages - shared containers.

Why not read the manual? The Designer's Guide pdf has a whole chapter on Containers.

Just the normal 'dsjob' command with '-jobinfo'. A Sequence (no 'r') job is just another job so no need to treat it any differently.

That's probably not a 'more than one space' issue - I'd wager you have nulls in one (or more) fields. Concatenating nulls into a string results in a null as the result.

If you just want to trim out all 'extra' spaces, the trim function will do that.

You would need to wrap them in code tags to preserve the spaces. By 'remove' do you mean 'reject'?

Of course, but... didn't want to go there.

Escaping them with a preceeding 'back-slash' would work.

BUSetup\(1000001\)20071119_200002.xml

Yes. BTW, Index() returns the position where is finds the substring within the string so you can leverage that fact in the constraint. Index(DSInput.Code,'U',1) equates to TRUE when a 'U' is found in the string and FALSE when there are none found. Combine that with the Not() function to reverse it i...

And why is that? What failed about it? Please post your syntax if you want help troubleshooting as it should work fine.

As noted, you'll need to not use transaction grouping but rather a transaction size of zero. And then ensure that if there are any errors the job aborts, which will force the rollback. Various ways to do that - run with a very low warning limit threshold, use a reject link set to abort after 1 recor...

No such syntax. Investigate the Index function, it can be leveraged in this case.