DSXchange

Yes, exactly - Column Import. I always get those two mixed up!

Ah... that sentence was split up and I misread the "in the current working directory" part as just where dsjob was being invoked from. Good catch.

Have you tried this yet? Did it work for you?

Or they are made "safe" but again it depends entirely on what you mean by "special" characters.

There have been several posts showing how to use awk in an External Source stage to do that, here is one: viewtopic.php?t=141139

Haven't tried it myself.

It means you 'cd' to the Project directory where the job lives and then start the dsjob command from there using a full path:

I have no idea how many in total there may be, but of the three I can see all are accessible. Meaning, you click on the title and they play. What do you mean by you 'cannot access them'?

I would aim for the most straight-forward approach that fits the requirements. If all you need is the Aggregator, use it. If you need to accomodate other values, then take a more 'complex' approach.

I have no DataStage access and my documentation is at home which I am not, so I'm going to have to defer to the wisdom of others to answer that question at this very moment.

I figured there were multiple detail records and yes, what I posted will work for that. As to the header v. detail, I would just create a boolean stage variable that you could use in derivations or constraints as needed. Something like: svIsHeader: if record[1,7] = '#Header' then @TRUE else if recor...

Read it as one varchar column. Use stage variables to track if you are in the "#Header" or "#Detail" data. Filter out the 'noise' records from the data (headers, blanks) and use (may have this backwards) a Column Export stage to automatically parse the string into fields based on...

Not by default. Default output is a double which you can make a decimal. For string fields you need to find and enable the 'Preserve type' property.

How accurate are the data samples you posted? From what you posted, I don't see a need for anything other than an aggregator.

Group on the first field, take MAX() of the other two.

As the number of rows out is less than the number in you can't simply map ungrouped columns across. Typically one would use MIN() or MAX() for those columns so that only one value is passed per group.