DSXchange

Nothing there seems like an error. Are any of those fatal? Warnings? :? And can you give some specifics on how you are 'reading' the xml file? You've got a Folder feeding the XML Input stage but how is it configured? For example - are you just passing in just the filename and using the URL/Filepath ...

"Hi Ray"? Seriously?

That's a horizontal pivot aka columns to rows and oddly enough there's a stage for that.

What is the character set of both the source file and the target database? If you use another tool, say like Toad, to view the table are the values in the string fields still 'corrupted'?

Need more information. Since the FTP stage is metadata driven, you need to ensure what's defined in the stage matches the file it is attempting to source and it sounds like there's a mismatch.

Where are you sourcing the file from? What does the file look like?

There's no one answer, from what I've seen it can depend on the 'service plan' or contract you have with the carrier. It's typically bundled free nowadays but I wouldn't take that for granted.

Probably a bug. You should have skipped 8.0 and gone straight to 8.1 instead. Or at least get the major 'rollup' patches from your support provider for this release.

Me, I wouldn't advise the use of environment variables for parameters that need to change run to run. Sure, you can setup values like that but you'd need a Sequence job to pick up 'schema1' and then pass it to 'schema', etc. And a different one for the 'twos'.

I don't know why it wouldn't be, but I have no way to check and have had no such issue with 8.1 running on Linux.

OK, that's good. What directory? Best to run this from the DSEngine directory as "./bin/uv -admin" on UNIX or "bin/uv -admin" from DOS I believe. Does that make it work for you?

Where are you doing this? You should be running those commands from outside DataStage at the command line, not from any client tool.

If you are summing, there's also an option to get a (paraphrasing) 'Count of Non-Empty Values' or 'Count of Empty Values' from what I recall.

You old fashioned fuddy-duddy, get over it and catch up with the times.

It usually helps to post both the output you want versus the output you get, clearly labelling which is which.

I mean, helps us mere mortals, Ernie probably needs no such.

With some caveats, I would assume. Seems to me you'd have to be vigilant in keeping the two servers identical with regard to O/S versions, patch levels, etc - anything that could adversely affect executables brought over from another environment. That again, maybe that list is smaller than I think i...

Nice, thanks for posting that here. :D