DSXchange

As noted. Jeez, what does everyone do, just skip to the end?

Too true! Been awhile and (sorry) forgot to mention that as another option. I spooled the output from his utility to a db table so I could query the results.

So... a direct database lookup rather than a hashed file? The latter is preferred and much more consistant but you can do it direct like that as long as you understand the performance considerations. And since it's a sql query, it behaves the same as if you had run the "select x from y where z&...

As noted, that would be a support question.

Cute.

Mostly that's because that *is* the solution.

Use a modify operator to specify the value to which the null should be converted.

Make sure you understand that the C++ compiler only kicks in during the "compile" process when a transformer is involved.

Sorry, but you can't just come here and drop little one-liners that are obviously interview-style questions and expect answers. That's not how it works or why we're here. Plenty of other sites for that kind of crap.

Explain to us how you need to 'read' this column. Do you actually mean parse?

A value of 1 would mean to commit every 1 record, i.e. every record as it is written. You either need to use a zero or some amazingly large number you'll never hit. If what you wrote is actually a negative one, that's not supported.

Me, I'd start with a dictionary. They're not exactly terms exclusive to DataStage or anything.

You'd need either a pretty complex repository query or a good hard look at a .dsx export of your project. Once you find one you can find them all.

Good point, let's first make sure you have more than the most recent run actually available. I'm guessing that may in fact be the issue as you have to go out of your way to constrain things to just "the most recent run" and it sounds like you're not doing that.

Assuming you've done everything correctly, it's now time to involve your official support provider. Those variables are somewhat generic and each plug-in writer populated whatever they felt were appropriate and / or were actually available. Each one seems to be different and perhaps the Sybase one d...