DSXchange

Change the metadata to support the data.

I seem to recall Ray saying he'd actually done that on a test or some such. Sort of a Kobayashi Maru style solution.

You don't need a routine. Use an Execute Command stage to 'type' the sequential file and capture the $CommandOutput, using it as a parameter in a downstream job.

Yes, it's been an issue for some time now. I need to constantly keep an eye on things when I post and either press 'Stop' if it is 'taking too long' to post, that or go back and remove the duplicates after posting. It's not consistent either, so I don't get it. It can work fine one minute and then h...

The trim function has now been suggested more than once, including within seven minutes of your original post last week. Did you even try it? Or read the Help for it?

All true. I've had people that didn't *like* the way DataStage formatted the output but they could certainly process it. And the only reason we 'needed' to pretty some was for the people on the other end, not the parser - as noted, it could care less.

Wow... that's a real word (or at least mostly real) and means just about what I thought it would mean. "a factitious word alleged to mean 'a lung disease caused by the inhalation of very fine silica dust found in volcanoes' but occurring chiefly as an instance of a very long word." It was coined to ...

Not sure what you mean - the last parameter to the -logdetail function is the entry number you want. So you get the range from the summary function and then iterate through the range and pull all of the detail entries.

D'oh... this is what happens when you get distracted and forget to click 'Submit' for 10 minutes.

The documentation shows the two options the command supports: -type to control what message types you want and -max to limit the number of records returned. You'd need to pull a log summary and then use that to determine what information you want, what range of message numbers is needed. Then use th...

Or it may be a stage limitation on the size of the SQL.. which stage?

You can't AFAIK, but perhaps you can split it into multiple parameters. Where are you using this?

Specifically, set the Read Method to File Pattern.

Turn off / disable the 'Generate formatted output' option. The way that DataStage formats XML output is... let's leave it at 'different'. So turn it off and if for some odd reason your 'end user' still doesn't like it, you'll need to find an external tool that will 'pretty print' it for you before y...

ray.wurlod wrote:I heard today that Massachusetts residents currently have 37 words for snow, not one of which is printable!

And eastern Australians for 'flood' as well, I understand.