DSXchange

Unless the job was created under a different configuration file no, because there are no pools mentioned in the given configuration file.

Oh, yuk! Use a server job, or a BASIC Transformer stage, with Oconv(TheString, "MCP") to identify non-printing characters. Other Oconv conversions can identify characters in the extended set, or you can use the UniSeq() function to get the actual code.

My bad. But it's not about Japanese characters.

Look in the DSINCLUDE/JOBCONTROL.H file in any project, search for the token DSJE. BADSTATE (which equates to error code -2). This indicates that the job is (was) not in a runnable state - perhaps not compiled but more likely aborted or stopped and not reset.

What speed do you get if you do no lookups? Maybe the bottleneck is in the stream input rather than in the reference input.

Can you import a table definition from Oracle? If not, get your DBA to check your connectivity from the DataStage server.

It will solve the "problem" of the corrupted job log, but it will mean that you lose any information already logged. If that is acceptable then the CLEAR.FILE command is the fastest fix.

Welcome aboard. This message is not about Japanese characters (which are read simply by specifying correctly how the characters are encoded, for example Shift-JIS). This message is about the fact that the delimiter character between columns has not been correctly specified in the Format properties o...

Who or what sent the email? Track that down.

Invoke the script that you would use if you didn't have DataStage, probably using Execute Command activity in a sequence or a before-job subroutine invoking ExecSH. There is nothing in DataStage itself that does what you require. The FTP stage does have before/after ("telnet") commands, bu...

Beware that any such change is a global change. Please explain what you have tried so far, so as to eliminate unnecessary guesswork on our part.

Something in Transformer stage XfmTransform, or in a routine called from it, is explicitly specifying three-way partitioning.

Only by changing the specification in the NUMERIC category of your locale.

As far as I am aware this is the case. After all, what you're creating in a Build stage is a new Orchestrate operator. Links to many libraries are automated by compiling within the GUI (note too that you can override the default set of libraries within the Build stage itself, as you can within the T...

How would you do this without DataStage? You use precisely the same means when DataStage is in the mix.