DSXchange

Perhaps Ken will explain his reasoning. Oh sorry... perhaps Kim will explain his reasoning.

I heard a rumour that you might be posting something like this...

Can't say that I've noticed this going on, perhaps it's off in forums I don't frequent all that often. Interesting. I shall poke around. Computer, perform exact match for 'rumour', please.

More than likely, there wouldn't be a 'previous' job handle to connect to. As noted, you should be able to use the other job name in the call to DSAttachJob to establish a new handle to it for your use. Of course, this all depends on exactly what you are planning on using this for and when/where you...

Alternately, you might want to post why you think you need to do this. Many people here would be more than happy to suggest alternative approaches that may work out better in the long run for you.

Conversion is implicit in DataStage Server, it's not tightly typed like the PX version is. So the answer is to simply move the value from one datatype to another. Now, if your Date is stored in internal format, you'll need to use OConv along the way. If that doesn't help, you may want to provide som...

'Best' is a relative term. It would certainly work and Mark has probably already gone and done exactly that. Just trying to discover some alternatives. Kumar - as an aside and just to be a little anal, you seem to be awfully fond of the little 'rolling eyes' icon. Not sure if you understand the conn...

Check your online help for the DSExecute command. This can be used to run operating system commands, including scripts.

Search the forum for 'microseconds' and you should find some recent conversations on this very topic. From what I recall reading, this is an issue with the base product and needs to be dealt with using some custom code.

No, that's one of the 'problems' with shared containers. There's no way to get performance statistics for the stages inside them.

One such place would be the Oracle OCI Stage Guide. You've got to enable DS_ENABLE_RESERVED_CHAR_CONVERT and then # is represented by _035_ and $ by _036_ in the metadata. They suggest you do this and then import the metadata so that DataStage can handle the conversion for you. Don't know if any suc...

Oh, well. Close but no cigar.

Yup.

I'm asuming it's trying to tell you that the semi-colon at the end of the query is the 'illegal symbol'. Remove it.

Pivot stage.

Can't you use one of the Transformation Settings on the Output tab to 'Replace empty values with NULLs'? Seem to recall something like that in the stage...