DSXchange

It has to be something with the display limit. Do a wc -l at the unix level and see what is the true count?

Look at you guys, heheh. The OP does'nt even know what hit him, or her

Never used them and hence cant help you? Did you go through all the prliminary steps in the installation? Anything needs to be added in the registry files (environment variables)? Did you stop and start the dsengine? If after all that it still does'nt help, call support.

Import your table using orchestrate 'orchbutil'. Thats more accurate.

On Unix you can stick a '&' in between the commands to fire them simultaneously. Try that on DOS.

24 must be the limit on the sequential file stage when you hit view data. Increase that to 9999, which I think is the max you can go, it will pull up everything, atleast in your case.

Can you pull up the data using 'view data' in your server job that built this job? Whenever you build a flat file, all fields need to be char and length should be given properly.

Vincent has a blog on it I believe. Plus there are other references here. Search for it.

Psst....no hijacking It will depend upon the complexity, as Ray mentioned.

Vick, yet again there is a need for a C routine

Sybase variables need to be set in the dsenv file for it to work properly and I bet the client needs to be installed on the datastage server. What about the DRS stage?

Have you tried searching on the error message?

Do you mind expanding on SME? Or atleast tell us where you heard about his term and in what context.

Look into ICONV/OCONV functions. You need to seperate the date and time part. Appy these functions seperately and concatenate them together.

ganesh123 wrote:okie dokie got it. Thank you sir.

He says oki dokie. He is funny......