DSXchange

Where are you specifying this- I would put it in the column defaults, you get to them by right-mouse-click on the column name and then "edit row".

Try "0x20" or just a space in that field.

Sumeet, the "record id" is the key to your hashed file. It cannot be an empty string or a null value.

The VOC file is the core file around which a whole account revolves. It stands for VOCabulary and it contains entries that point to all the Verbs, PAragraphs, PHrases, Files and other types of keywords that a DataStage account uses.

I'm glad you've solved your problem. The value 46 is that of "&" and since it doesn't lie in a part of the chart where arabic characters are the translation error probably occurred there. But it's a moot issue now that you've solved it using other means.

Rajesh - you need to go into your mapping tables and see if the numer value that is displayed with SEQ or UNISEQ corresponds to the arabic characters that are displayed. Very often the problems with NLS are actually problems with displaying the characters, which is why I asked you to display the act...

You have a couple of possible sources of your non-ASCII data being converted incorrectly; and you need to understand your data before narrowing down the cause. 1. Do you know your Access database column character set? Is it just a Unicode representation or something else? Do you have an NLS enabled ...

Didn't Mathieu answer it for you?

Kalpna, did you try both "MCT" and "MCN"? You received 2 answers within 10 minutes of posting your original query and asking for another answer straight away? Since you know that the whole string is to be lowercase except for position 6 and you know that there is an UPCASE() and a DOWNCASE() functio...

One of the options in your sequential file stage is to include the columns names as the first line in the output. I'm not sure if it is a tick-box in PX as it is in Server, but I do know that the option exists in the stage since I've used it before.

I'm not a DS machine right now, but I think that using a OCONV({YourDateString},'MCN') will do an initial capitals conversion for you - it's normally used for names and the like but I think it will ignore leading numerics.

The export needs to be done on the client. If you have ftp installed you can FTP the .dsx export file wherever you wish; but I'm not quite sure what you mean by doing it with FTP?

I'm not sure that this is going to help you - most projects will use parameters for such columns, so even by doing some complex searching of the repository contents you will end up with just a list of parameter names and not necessarily the actual values used at runtime. I like using a .DSX export f...

Wolfgang - we shouldn't be so Euro-centric and should add in all those South American, Middle-eastern as well as Asian holidays as well

How about turning your echoing on in your script to get more information on the error?