DSXchange

Show us exactly how you set everthing up in the job / stage to use environment variables for the file path.

OK, found what I was thinking. Check the XML Pack Guide pdf and the Writing output to your file system section of Chapter 4. You'll see mention of these 'column index flags' there:

%% Column position, starting with zero (0)
%@ Column names

The latter may help you.

jwiles wrote:You should ask the data provider for the specifics on how the date is formatted.

This.

A Server job using the Folder stage can get that for your XML, that or a Server Shared Container with the same in your parallel job.

Done.

FYI, split from this thread on Data Lineage.

Was guessing it is a vertical pivot since they said it needed to "pivot to ten columns".

Been pondering this and I believe that new environment variables may have been added to control this, at least to some degree. Let me see what I can find, or perhaps Ernie will stop by.

That's how it works.

My 'workaround' in the past was a post-process that renamed all of the split instances with the names that I needed them to be.

Thank goodness you said something because I was gonna fix it for you!

True. Another point to note is that we are required to archive the source files on our side (in spite of them still being there on the source, go figure) so "need" the phyical copy we get from having them FTP them over.

And yes, YMMV.

I'm of the opinion that you are better off having the host system FTP the file to you. Typically the simple and easy route and you don't have to use that darn metadata driven stage. Added bonus is that they should be able to automatically convert it to ASCII for you.

Specifically, 'Chapter 3. Planning Step 3: Designing an Installation Topology' lists (and details) the various topologies.

$DSHOME/include/dsapi.h

Why not try it and see? Create a small test case, put it through the wringer and let us know.

OK... it's been awhile but since there is only one log that all instances share and I thought I recalled that the Director uses what is basically a view into that log to show what happened for each instance run, I thought I remembered that purging the instance specific records from the log would rem...