DSXchange

Decimal, not Octal so "009". Assuming that's where you were going wrong.

Pass in the parameter name correctly and it should work fine. Right-click on the stage, select Grid Style and then use the Insert Job Parameter widget to populate the fields.

Yes, you can use job parameters for all of the connection information in that stage.

Basically by keeping track of how far you got and then, when restarting, constrain your process to not start passing records until you get up to that point again.

Hopefully using the term correctly - I mean substituting a unique known value for the NULL, say like a "*", then making the same substitution when querying.

All that really matters is if it helps you.

Thanks for the closure, though, future searchers thank you. From the future. Later.

Hmm... the syntax doesn't seem to be valid and I get the same error running it for an RT_LOG in my project. And I ain't smart enough to know what the correct syntax should be.

Timezone (TZ) environment variable problem?

Another option would be to have not allowed NULLs into the key, perhaps by using "in-band" null values if they couldn't be constrained out.

Ray gave you the syntax.

TP wrote:Yes I do get the "from previous run"

You need to post the contents.

What happens if you change the metadata to LongVarchar?

Not if you want to solve the problem. Or read the first post.

Let me be more emphatic - this is not possible from the command line.

Did you have any problems occur on Monday that you are aware of, particularly the partition where DataStage is installed running out of space for example?