DSXchange

As noted, Array Size controls how many records are sent at one time across the network to the database. The setting for Transaction Size controls the commit level. While some of the native stages (OE) use environment variables to control that, I do not believe that the ODBC stage does, there should ...

Have you not been through the functions listed in the documentation, either in the online help or in the suppiled pdfs? In addition to the ones you've been asking about, there is an IsValid function you should check out as well.

Have you verified what column INDEX IAR102X2 is over? It does not allow duplicates and somehow you are sending duplicates in that column, according to the error message. Also, please let us know what settings you are using in that stage and perhaps even post the sql you are using.

That's exactly what I have done in the past, typically a Server job is perfectly suited for the task of gathering parameter style information even if the main processing 'needs' to be done using parallel technology. Then a Sequence job can easily parse apart the delimited USERSTATUS information from...

Details, please, especially the options you are using in your target stage so we have some idea exactly what kind of 'load' it is doing.

Right, just do it directly, there's no need for any kind of 'wrapper'.

You've got the main guides, there really aren't any other documentation sources other than the individual pdf files for the plug-in stages - there should be one for the RDBMS one as well.

Do you have any specific questions on the stage we could answer?

Put it in a custom routine and then call that routine in the UserVariables stage.

No, nothing in the GUI will allow a multi-selection of jobs to be run since each must prompt for run time information / parameters.

What does that mean, exactly? An exact search for your full error message returned 134 matches and I'm sure they all "open up" just fine.

Can you be more precise on the problem you had with the search?

It won't make any difference, they are equivalent. The problem should only be happening if your connection "breaks", takes a less than graceful exit say via an End Task or a crash of the application. Otherwise it really shouldn't be happening on any kind of a regular basis. Well, unless yo...

Still think it would help if you answered my questions.

Project Locked is completely different from a license exceeded issue, the latter will simply tell you that. The former is a resource issue with the lock table from disconnects and crashes (typically) and needs to be cleaned up, either manually or automagically, as you have been doing.

IConv/OConv would be a Server solution. I'm curious, is that an accurate representation of your incoming data? Specifically there's no space between the month and day? Is the month name always a fixed length of three?

OK, then how about the point that Vincent made?