DSXchange

Let's see - you've posted the same code twice and stated that it is urgent. This means you haven't read the readme's plus you've most likely not bothered trying to use the Search function either. This means that this isn't really an urgent issue.

Yes, the IPC stage is no longer necessary, you don't need a sequential file stage to replace the IPC, just remove the IPC stage altogether.

Could you explain how the program is getting this string - is it from a job parameter, and if so, how are you setting the value at runtime.

Posting the same question more than once won't get you any additional or bette ranswers. In fact, chances are that you've lowered your chances.

Have you tried surrounding your parameter with another legal quote character - i.e.

Implementation is defined as Spelled Pronunciation[n. im-pluh-muhnt; v. im-pluh-ment, -muhnt]...5. to put into effect according to or by means of a definite plan or procedure... ; Your 'implementation' instance is misnamed, thus causing the confusion. Perhaps "test" or "SIT" or something like that i...

I can't recall - why don't you try it without predefined columns to see? If it doesn't work you'll have your answer.

Could you perhaps rephrase that? You do need to define rows and columns so that the ODBC drivers can detect them and access them; if that is what you are asking.

I think that the server DB2 stage expects the date and time to be in DataStage internal format. Try
ICONV(In.EN_DATE,'D4-YMD')
ICONV(In.EN_TIME,'MTS')

Moderator - please delete this duplicate thread

Please post in the correct forum and add what you have tried (i.e. reading the documentation, searching the forums)

use the dsjob command with the options you would like and redirect the output to a text file.

Good, that means that my earlier assumption is proven wrong!

AmeyJoshi14 - have you checked your log file in the director to see if you can see the row counts there?

As I mentioned before, you can use the DSGetLinkInfo() and DSGetStageInfo() calls to get this information from inside a DataStage DS/BASIC routine (which can be run in a before- or after-job call).

I will assume that "did not recognize the record" means that the derivation returned a '0'. This means that the string does not contain a char(226) character. Since you assert that it the source does, this would mean that your NLS settings have remapped the character. If you know the record and posi...