DSXchange

It would be more interesting had Chandra advised the data volume on which the test was done, and if the Column Import stage had been user rather than a Transformer stage for the parsing.

Buffering parameters are set using environment variables. I suspect the culprit here is APT_BUFFER_FREE_RUN (but do check with your more experienced colleagues as to why this may have been set at 0).

Please post the resolution, which I suspect was simply to provide the argument in the form jobname.invocationID

I note also that you're using 64-bit libraries. Do you have a 64-bit version of DataStage?

Look in the job log for the sequence. Were job run requests for the parallel jobs even issued? If not, something in the logic of the sequence is preventing that. If they were, check the job logs of the parallel jobs themselves. Tip: you can jump to these from the log of the sequence; on the job run ...

You could use the job's user status area as that variable. But you would then need to retrieve it using a routine that invokes DSGetJobInfo() function. Messy, but doable in a server job.

Information Analyzer runs on the "DataStage" engine. Therefore Robert's suggestion may be apposite.

I too have had problems importing WSDL that had namespace labels in the lowest level elements. Replacing these with actual namespace URLs (suggested by Ernie Ostic) allowed the WSDLs to be imported.

Have you tried using Change Capture and Change Apply stage types?

What happens if you invoke Help (F1) with the stage open?

The Big Data stage is very like the Sequential File stage. The "file" to which you point it is a reference to a file in a Hadoop file system.

Does your routine generate a double free(), as the error report indicates?

You have a single digit day part. Your mask specifies two digits for day. How does your data represent 8 Aug 2011 and 28 Aug 2011. You need to organise matters such that the format of the string you're converting matches the specification given in the conversion function.

The Checksum() function should achieve this result for small enough strings. (There's also a Checksum stage but I can't recall whether this existed in version 7.)

Congratulations on solving this. I am not aware of any such requirement being documented.

Are you logging in as a user with DataStage and QualityStage Administrator role?