DSXchange

Its 999. Refer here

Ok. Let them be inserted with blocks. Do a select on this table and then load it to a flat file or send it to peek stage. Do you see those blocks in the file or log file? Do you have NLS enabled at the database and not datastage?

No. The sequential file properties "quote character" is something totally different. The OP gave us sample data that shows very clearly that the data has two fields, the "ID" and the "Name". The name has quotes within the data, inpite of surrounding the data. Hence the quote character option within ...

No. It wont. That test was just to make sure that you were actually getting 'space' as a pad character.
What if you change your target sql type to varchar. Does that take care of the problem? The database will put the necessary spaces itself.

What happens when you load a few records to a flat file or dataset? Do you see the block characters there too?

Yea, do an "order by clause" on this unsorted table and load it to a flat file. Pass a truncate on the table and reload the sorted data.

I love posts like these, makes me laugh. Especially after Craig has answered to it,

Then there is something fishy in the data.
Try the following and see what the following shows in your output

Each stage has its own functionality. Some functionalities can occur in different stages. I know of no such document, besides going through archives and learning for the suggestions of our gurus here. For eg: a modify stage is to be preferred over a transformer. Sort stage over in built sort operato...

Welcome Aboard
Please avoid using words that demand urgency. This will only delay your response. Since you are new I will cut you some slack.
You can look into the CONVERT() function in the transformer stage.

I know Kim was talking about bulding such a tool a couple of years back. Dont know what happened to it. I know he had built a DataStage to PLSQL and DataStage to VB converter. Dont know about conversion between tools.

Was there any other error/warning message? Did you try searching on the error message?

Basically the first number tells you position and the second number tells you the length from that position to substring. The very same method is available in server jobs too.

See if this post helps.

1) As long as the comma is inside quotes, it should be fine, no matter how many commas you have. I am sure you can tweak your logic to handle that. 2) You need to choose your quote depending upon the data. If the data has single quotes, then choose double quotes for surrounding varchars that contain...