DSXchange

Interesting... thanks for posting your resolution.

Seems to me you have two different feasible options:

1) Contact support
2) Reinstall from scratch

I would imagine via ODBC, have you looked into that at all? And in case this helps: MemSQL is MySQL wire compatible which means there are many freely available open-source clients, connectors, and development tools that work with MemSQL out of the box. The availability of these tools saves expensive...

I don't believe so... sounds like a support question to me.

... and then moved to the proper forum.

Hey, People Of Earth Who Have Actually Done This Before... as in use this stage as a target, feel free to jump in and add your expertise.

Wait... and then comes The Sundered Grail right? Loved that series.

Your English is just fine, no worries there. I haven't worked with the Unstructured stage writing to Excel but have done other things interfacing with it and Excel is a bit of a harsh mistress. It doesn't really have "varchar" fields per se unless you are saying they end up as Text fields ...

Parameters don't work differently there than anywhere else so not sure what it is you are asking. Why not try it yourself then tell us?

Sorry but I'm not really following what the problem is that you are having. What "doesn't work" when you use RCP for this? And by saying you are "dynamically selecting columns" does that mean you need RCP for this as the number of columns and data types change from file to file?

Ansul29 wrote:Only issue was parameter was in parameter set

Ah... knew we were missing something. Kudos for figuring it out.

Meaning... you are wondering if an Execute Command stage in a Sequence job can access a remote directory and move the files locally? If so, the answer is yes. I would suggest you get it working from the server's command line first before you even attempt to fold it into a DataStage job.

Ditto.

In your shoes I would test the 'normal' status results and then, knowing my mechanism was sound, would sleep soundly at night knowing it would catch the outliers as well.

Can you verify the job type, please? I don't recall Server jobs having a "File Pattern" option in that stage but could be wrong.

Which is why I was thinking they needed to go 'before'... but a quick search seems to imply that they are for use in stored procedures rather than SQL.