DSXchange

It would seem that you declared your compiler command to be "/usr/lpp/xlC/lib" in your Administrator.

I'm not in a position to check and don't remember the details, but I recall about a year ago we had issues with XML namespace definitions and installed an IBM patch that addressed the problem.

How about a transform stage substring derivation of "In.Column[1,9]"

Did you try the transform stage to see if the error is also present?

Bireswar, there are a lot of DSXChangers who would help you, but only if you define "facing a problem". There is a very big and very fundamental difference between a NULL string and an empty string; once you get a grasp of that the question will most likely answer itself. A NULL string is ...

If you explain what you mean by "link" you would get a better answer. This type of functionality has been done often in the past - but there are many means of solving it. Usually you have a Job Sequence which calls a job that access the tables to get the appropriate parameter values. These...

The TRIM function, while usually called with only one parameter, has several options that are quite handy. In this case, you could do a This means trim all leading 0's from the column "In.NumberColumn".

If you make a copy of the job and remove the new stage, does it compile again?

If the conversion can't be done then a null is returned - so you have just masked the error and not solved the real cause.

"records" and "rows" are meaningless by themselves. How many Mb or Gb must be transferred? What are you writing into and where are you reading from?

From UNIX, try the commands What are the results?

That looks strange. Can you put a transform stage in there and attempt a type conversion on DSPROJECT_ID there for test purposes?

With NLS there is a possibility of having different code points pointing to a character depicted as a space. But in an NLS environment the TRIM() function will most likely remove them as well, unless you do a specific TRIM(String," "). But if you make that change, you might as well use arv...

Well, the first message refers to the MAXMEM setting (see http://publib.boulder.ibm.com/infocenter/comphelp/v7v91/index.jsp?topic=/com.ibm.aix.pli.doc/ibmx2mst64.htm ). You can also manually try the c++ compile call listed later to see what message you get. (oops, I see the link I posted goes to the...

If you have autopurge set for this job, try turning it off and seeing if the error goes away.