DSXchange

Problem is it's deployed as a service, which usually means "always on" and so never commits until you shut it down or commits every X records regardless of what's going on. That's why we went with Server jobs and a single ODBC stage since it supports multiple links and doesn't care if all ...

That's what "dsjob" is for. That's the command line utility that, amongst other things, allows something outside of DataStage to run jobs.

You could always use the 'Set defaults' option under the Job menu in Director to set the proper runtime defaults. That rather than constantly overriding the design time defaults.

They will be in sequence, what they may not be is in a contiguous sequence - i.e. there may be "holes" in the sequence but that's not an issue for a surrogate key. Think about it - there's no way the stage is checking that entire list every time it issues a number to ensure it doesn't re-i...

A Date datatype doesn't have a format. You don't have a Date, you have a string in "dd/mm/yyyy" format. That's why it works when you declare it as a Varchar.

I would imagine that a state file holds the same information that a sequence or other 'generator' type object would in a database - the most recent value.

That's... silly.

No, everything should be there. What contents do you believe to be missing?

Refer to the ones that ship with the product. All of the routines have source code available for browsing with a double-click.

I've done this in a Server job using a single ODBC stage and issuing an explicit 'commit' or 'rollback' when needed. No clue how you would manage that in a PX job where you have to use multiple stages.

From my quick search, the advice is to make sure that both DATASTAGE_JVM and DATASTAGE_JRE are set properly.

There's no dsenv file with a Windows server, that strictly a UNIX thing.

Ha! I knew about the first but not the second. :D Too often people here post questions focusing on what they believe to the the solution to their problem without actually mentioning the problem they are trying to solve, just the error they got in their attempt. It's always better to provide the &quo...

I have no idea but this may make a difference, so I'll ask - is this an 8.0 or 8.1 installation?

Why for? It's not a "file" but rather a database table in either the XMETA repository or the Universe one specific to the project, depending on your 8.x version. For 8.1 they're all in XMETA by default.