DSXchange

For Server it is typically:

Folder -> XML Input -> Transformer -> Sequential

Check Kim Duke's website under his Tips&Tricks page you'll find an XML Best Practices document that he is hosting for us. Invaluable reading.

I don't believe that you can, but happy to be proven wrong.

Read the help for the "-log" option, while it *is* used to write to the log it's not what you are looking for. You just need some standard UNIX redirection of standard error to standard out, I reck'n:
Off the top of my head.

No, it's not per user but rather project wide. And should have mentioned that you need to check as the 'administrator' user, typically 'dsadm'. So the fact that it is enabled for the administrator shows that NLS is enabled in the project. And you can click on the button to see the currect mapping. I...

You should be able to check via the Administrator - there is an NLS button on the main General tab. If it is enabled, NLS is, and vice versa. This is in earlier versions, not positive how it all looks in 8.x or if there is a "better" place to check as I don't have access to that version.

Try changing the "\" to "%5C":

DomainName%5Cuserid

Was your source table altered in any way?

srinagesh wrote:Theoritically & Programatically this type of looping should work fine, but for some reason Datastage does not seem to like this.

No, it doesn't. You cannot build any kind of a "looping" structure in your jobs, Parallel or Server. Knock off the fancy stuff.

I would think that information would be up in the 'top' of the .dsx file.

OK, "either one" meant the ones mentioned in your subject - IVVM.LIC or DDVM.LIC - and since the former does, I'm unsure why you would be getting that error unless (perhaps) it has become corrupted.

Is this error consistent? Does that ODBC connection work for anyone else?

And does either one of those filenames exist in your "branded_odbc" directory?

The limit. And an exact search for "resize" should turn up quite a number of discussions on this topic.

Closer to 2.2GB and writes will fail (and it may corrupt) when the limit is exceeded. Time to switch to -64BIT or investigate the "resize" command to convert an existing 32bit hashed file.

Welcome. Not really what I'd call a small issue, heck Oracle doesn't really support LONG fields all that well, too many restrictions on what you can and can't do with one. I'm guessing this is a 7.x (or earlier) Oracle database? There really aren't any 'transformations' you can do on a LONG, so you'...

Welcome. You can, and as you noted typically by omitting the column. What database? What have you tried and what specific issues have you seen?