DSXchange

The 'old' ones work just fine. I've used them to generate crap tons of XML for Google and Yahoo in the past.

I'm going to mark this as Resolved as that's really all there is to it, but if you have more questions on the subject - come back. Open it back up. Ask away.

And, from what I understand, not usable in a Server job... but could be wrong!

No, not as stage variables. While you can assign parameter values to stage variables, that's not how you get them bound into the source SQL. For that, find the place where the variable needs to be and use the parameter name (correctly cased) enclosed in hash signs there: select a from b where b.LOAD...

It would seem... no. Perhaps?

viewtopic.php?t=155356

Seems to me to be a question for your sales person. Unless someone here knows definitively, that is.

Perhaps more of an alias or cataloging issue. But then I've never used DB2, only... Google.

For future searchers, you resolved this by doing what exactly?

kumar11 wrote:This likely indicates a network problem.

Did you investigate this?

And without going into all of the normal lecture behind it, for #1 you do not need the value to be 'always unique'.

That sounds right, hence the occasional need for that APT_NO_INSERTY_TSORT environment variable when you don't want that to happen.

Please include your complete error message.

Note that the reply is specific to partitioning only, the sorting is still up to you from what I recall.

As has been noted many times here, Auto is guaranteed to always provide correct results. Wouldn't make much sense otherwise. However, and as also noted, it may not select the most efficient method for the stage. Found one of Ray's posts on the subject where he lists what Auto defaults to by stage: h...

Ernie, thanks for the clarifications and insight.