DSXchange

매우 흥미로운

Perhaps equivalent but the officially documented InfoType is DSJ_JOBNAME with an underscore. There's also a macro you can use.

Yes. You can call it from a BASIC Transformer or a Server Shared Container in PX jobs. Or you can rewrite it.

... and here we are in the proper forum.

... if you are certain that it is a space and not something more typical like a TAB.

There's no aggregation needed here.

If you don't need to preserve the input order, what about using a Sort stage and having it add a group change key? You could then do what you need in stage variables after that.

You use the StringToDecimal() function. Show us your syntax and some samples of the incoming data. Also, are you saying that you always get zeroes regardless of the original string value?

No worries, that message was for everyone - not picking on you specifically.

Hargun, you know the drill by now... what have you tried? What problems are you having? Your requirement seems pretty straight-forward so far.

Do you need to preserve the original file order? That's the only thing that might make this a little tricky.

Cleaned up your example. :idea: People, please remember that you MUST use code tages if you want to preserve white-space in your super duper examples with (for example) columns of data. Otherwise the forum software removes all of your 'extra' spaces. It has been doing this for years, learn to love t...

I'd also like to know your exact version of DataStage.

Being "new to XML" could turn this into a long and painful conversation as it's not really something you could learn in a forum post or twelve. Is there anyone you work with who knows XML and could help? Most of what you'd need to do is not specific to DataStage, so don't let that scare so...

Typically, that would be a stored procedure written by the DBAs that you would have execute grants on. It would have the grants needed to do the truncate and could handle any RI constraints as well.

I'm not sure if there is anything you can do about it other than manually edit it afterwords. You may find that you need to leave it that way when dealing with multi-byte charactersets, however. If your instances use "byte semantics" then this may be a needed workaround. Specifically, when...

clarcombe wrote:As for the NLS_LANG, can different databases have different NLS_LANG values specified ?

Instance level.