DSXchange

Why do you want to do it there? And that sql would change everyone's Name to 'Gaurav', is that really what you want?

The Field() function works the same as in Server, so you could use that for the first field and then a Column Import* stage for each record type could automagically parse out the remaining columns.

*Pretty sure that's the right name.

Define the record as one long string in the Sequential File stage. After you have the record in the job, parse out the first column and then you can decide how the rest of the column gets parsed after you have that value.

Do you know the maximum number of possible columns?

Any reason you can't "add" them? Run on more than one node to cut down on the lookup size?

Im really curious if There is some limitation with Windows 32 bit thats causing the problem Well... your "could not map" issue is definitely an artifact of a 32bit operating system - Windows or UNIX - and one that has bitten me in the butt in the past. Make sure you minimize how much data...

It executes all kinds of things, including any operating system command and you would specify 'UNIX' as the type for a shellscript rather than 'DOS' (etc). Is your DataStage server actually running on a UNIX box?

Please don't post the same question twice. If you need to make a clarification, do so by editing your original post (or replying to your yourself there).

Sorry but I don't see an actual question. Do you know the username/password (etc) of your queue? Know them but don't know how to "pass" them? Something else entirely? Please be as specific as possible regarding exactly what information it is that you need.

For Server, but the ODBC and UV stages support a lookup multi-row result set and it is a property of the reference link itself.

DSExecute()

We're moving too far afield to keep discussing this in someone else's resolved post. Please start your own. And when you do, please be sure to include details of the issues and messages you are having / seeing.

Ok, that should be good... is it all working for you?

By "turn off" I assume they mean "kill". The job has buffered a ton of log messages and they are slowly being written out... kill the remnant job process to stop that.

That's how it works. All it does it supply the file pathnames to the XML Input stage and that stage does the actual reading - as long as you selected the URL / File path option in the XML Input stage. Did you? What happens when the job runs?

That's because you are (as noted) confusing Transaction Size with Array Size. The former controls commits, the latter simply is the number of records sent to the database at one time.